Memory corruption via dangling HTTP/2 header buffers
Published Sep 20, 2026 · Updated Sep 20, 2026
Use-after-free in Suricata before 8.0.7 allows remote attackers to corrupt memory through inspected HTTP/2 response headers. Http2ThreadMultiBuf frees and reallocates owned header buffers during a second rule-list pass, leaving pointers used by later DetectRunPrefilterTx checks dangling. Triggering requires one transaction to be inspected by http.response_header rules both with and without a transform; the vendor has not published a more specific operational outcome.
Summary
What happened
Use-after-free in Suricata before 8.0.7 allows remote attackers to corrupt memory through inspected HTTP/2 response headers. Http2ThreadMultiBuf frees and reallocates owned header buffers during a second rule-list pass, leaving pointers used by later DetectRunPrefilterTx checks dangling. Triggering requires one transaction to be inspected by http.response_header rules both with and without a transform; the vendor has not published a more specific operational outcome.
The record
- CVE
- CVE-2026-94084
- Published
- Sep 20, 2026
- Updated
- Sep 20, 2026
- Vendor
- Open Information Security Foundation
- Product
- Suricata
- Classifications
- CWE-416, T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2026CVE publishedPublication date reported by the CVE source.
- Sep 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <8.0.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started