CVE-2026-45759
largeDoS in Suricata via expensive parsing of large HTTP Content-Disposition headers
Suricata, an open-source network IDS/IPS and network security monitoring engine, contains an uncontrolled resource consumption flaw (CWE-400): during HTTP response body processing it can repeatedly perform expensive parsing of very large HTTP `Content-Disposition` headers. An attacker able to send crafted HTTP traffic through or to a monitored link can trigger this repeatedly, causing excessive CPU usage on the inspection engine and a denial of service. The impact is availability-only (CVSS 3.1: 7.5, AV:N/AC:L/PR:N/UI:N/A:H); there is no confidentiality or integrity impact. Any organization running Suricata before 7.0.16 (7.0.x) or before 8.0.5 (8.0.x) that inspects HTTP traffic is affected. There is currently no known exploitation in the wild, no public proof-of-concept, and the issue is not on the CISA KEV list.
What to do: Upgrade Suricata to 7.0.16 on the 7.0.x branch or 8.0.5 on the 8.0.x branch. If upgrading is not immediately possible, deploy the documented bypass rule (alert http1 any any -> any any with http.request_header; content "Content-Disposition:"; startswith; bsize: > 8192; bypass;) to skip expensive parsing of oversized Content-Disposition headers. Audit whether your sensors inspect HTTP traffic on untrusted links, since only HTTP-inspecting deployments are exposed to this CPU-exhaustion vector.
| OISF (Suricata project) Suricata | all versions prior to 7.0.16 in the 7.0.x line and prior to 8.0.5 in the 8.0.x line; fixed in 7.0.16 and 8.0.5 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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 could repeatedly perform expensive parsing of large HTTP `Content-Disposition` headers during HTTP response body processing. Crafted HTTP traffic could cause excessive CPU usage and denial of service. Versions 7.0.16 and 8.0.5 contain a fix. As a workaround, use a rule like `alert http1 any any -> any any (sid: 1; http.request_header; content: "Content-Disposition:"; startswith; bsize: > 8192; bypass;)`.
- Weakness
- CWE-400
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
In the news0 stories
No ingested article mentions this CVE yet.