Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessControl or intercept an HTTP/2 origin server
-
DeliveryServe crafted high-ratio compressed DATA frame
-
ExploitSuricata sensor decompresses response body
-
ExecutionHeap buffer grows unbounded
-
PersistHost OOM kills Suricata process
-
ImpactNetwork monitoring/enforcement blind spot created
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Compression ratio limits
|
| Exploitation Conditions | Suricata must be actively inspecting HTTP/2 traffic, which requires that HTTP/2 application-layer parsing and decompression be enabled - this is the default configuration in current Suricata versions. The attacker must be able to route HTTP/2 traffic through a network segment monitored by the vulnerable Suricata sensor, either by controlling a web server that clients on the monitored network connect to, or by performing a MITM on existing HTTP/2 sessions. No authentication to Suricata is required, and no client-side user interaction is needed beyond the client initiating an HTTP/2 connection. Exploitation is limited to networks where Suricata is deployed and where the attacker can influence HTTP/2 response content visible to the sensor; deployments with HTTP/2 disabled (via workaround) are not affected. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H scores 7.5, which accurately characterizes the risk profile: fully remote, unauthenticated, zero-click, and trivially repeatable with no special conditions beyond routing traffic through a Suricata sensor. The impact is purely on availability (A:H), with no confidentiality or integrity consequence. No CISA KEV listing and no public exploit code have been identified, keeping this below immediate emergency priority; however, the attack is straightforward to construct - any attacker who can inject or serve HTTP/2 content through a monitored segment can trigger it. For organizations where Suricata is deployed inline as an IPS, a successful attack removes network visibility and enforcement, which is a significant operational and security consequence. EPSS data is not provided; absent it, the low exploit complexity and high-value target (network security infrastructure) suggest meaningful real-world exploitation probability. Patching is the clear mitigation given the simplicity of the vector. |
| Exploit ScenarioDerived | An attacker who controls a web server reachable by hosts on a monitored network (or who can perform a man-in-the-middle on HTTP/2 traffic) crafts an HTTP/2 DATA frame carrying a small but highly compressed payload - analogous to a zip bomb - with a compression ratio of thousands-to-one. When a client on the monitored segment fetches this resource, Suricata decompresses the response body without bound, rapidly consuming available system memory and causing the IDS/IPS process to be killed by the OS OOM killer or to become unresponsive, blinding the network defense layer. No public proof-of-concept is required to execute this; the technique is well-understood and any HTTP/2-capable server can serve such a response. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 10, 2026
Memory exhaustion via decompression bomb in Suricata prior to 7.0.16 and 8.0.5 allows a remote unauthenticated attacker to crash or degrade the IDS/IPS engine by transmitting crafted HTTP/2 DATA frames with extreme compression ratios. The HTTP/2 response-body decompression path (supporting gzip, deflate, and brotli) lacked an effective upper bound on allocated buffer size, enabling a data-amplification (zip-bomb) attack against monitored network segments. No public exploit or active exploitation has been identified at time of analysis, but the low attack complexity and critical position of Suricata in network defenses elevate practical risk.
RemediationAI
Vendor-released patches are available: upgrade Suricata to version 7.0.16 (7.x branch) or 8.0.5 (8.x branch), as confirmed by the OISF security advisory GHSA-45p7-j5wm-8wrx and the forum release post at https://forum.suricata.io/t/suricata-8-0-5-and-7-0-16-released/6315. The official workaround for environments that cannot patch immediately is to disable HTTP/2 inspection in the Suricata configuration; this eliminates the vulnerable decompression code path entirely but will reduce visibility into HTTP/2 traffic, which now represents a large fraction of web traffic, potentially causing missed detections. If disabling HTTP/2 entirely is not acceptable, consider placing resource limits (ulimit / cgroup memory caps) on the Suricata process to bound the blast radius of an attack, though this is a containment measure rather than a true fix and may cause process termination under load.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Suricata (cpe:2.3:a:oisf:suricata:*:*:*:*:*:*:*:*), developed by the Open Information Security Foundation (OISF), is an open-source IDS/IPS/NSM engine that performs deep packet inspection including application-layer protocol dissection. The affected code path handles HTTP/2 DATA frame payloads that are compressed using content-encoding schemes (gzip, deflate, brotli). CWE-409 (Improper Handling of Highly Compressed Data / Data Amplification) describes the root cause: the engine decompresses these payloads incrementally into a heap buffer that was allowed to grow without a configured or hard-coded ceiling. A maliciously crafted HTTP/2 response with a pathologically high compression ratio - a classic 'decompression bomb' - can cause the Suricata process to allocate gigabytes of memory from a small on-wire payload, leading to out-of-memory conditions on the inspection host.
Know when Suricata gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Network-reachable decompression bomb requiring no authentication or user interaction; impact is solely availability via memory exhaustion, no C or I consequence.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to versions 7.0.16 and 8.0.5, Suricata's HTTP/2 decompression path could grow the decompressed response-body buffer without an effective upper bound. A crafted HTTP/2 DATA payload using a high compression ratio, such as gzip, deflate, or brotli compressed data, could cause Suricata to allocate excessive memory while decompressing the payload. Versions 7.0.16 and 8.0.5 contain a fix. As a workaround, disable HTTP2.
Technical POC Analysis
Evidence note: the supplied evidence is the GitHub Security Advisory GHSA-45p7-j5wm-8wrx only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Suricata network monitoring engines prior to versions 7.0.16 and 8.0.5 are vulnerable to remote denial-of-service attacks using HTTP/2 compressed data, potentially disabling critical intrusion detection and prevention capabilities. An unauthenticated remote attacker can transmit specially crafted HTTP/2 frames to crash or degrade the IDS/IPS engine, leaving monitored networks without active threat detection. Organizations with Suricata deployments should immediately identify affected versions and implement compensating controls.
Restrict HTTP/2 traffic from untrusted network sources at perimeter gateways; disable HTTP response-body decompression (gzip, deflate, brotli) in Suricata rules if not operationally required; implement real-time alerting for Suricata process crashes and sustained CPU/memory exhaustion indicative of decompression bomb attacks; enforce network segmentation to limit which systems can access monitored network segments.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Netgate pfSense CE Suricata Path Traversal Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vul
OISF suricata-update version 1.0.0a1 contains an Insecure Deserialization vulnerability in the insecure yaml.load-Functi
Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suric
An issue was discovered in Suricata before 6.0.4. Rated high severity (CVSS 7.5), this vulnerability is remotely exploit
An issue was discovered in Suricata 4.1.3. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, n
An issue was discovered in Suricata 4.1.3. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, n
An issue was discovered in Suricata 4.1.3. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, n
An issue was discovered in Suricata 4.1.3. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, n
An issue was discovered in Suricata 4.1.3. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, n
Open Information Security Foundation Suricata prior to version 4.1.3 is affected by: Denial of Service - TCP/HTTP detect
Suricata before 4.0.5 stops TCP stream inspection upon a TCP RST from a server. Rated high severity (CVSS 7.5), this vul
The MemcmpLowercase function in Suricata before 2.0.6 improperly excludes the first byte from comparisons, which might a
Same technique Denial Of Service
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
EUVD-2026-75508
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB