Quick answers
- Is CVE-2026-63452 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63452 being exploited in the wild.
- How severe is CVE-2026-63452?
- High severity, with a CVSS score of 7.5, published 18 September 2026.
- Which products and versions are affected?
- OISF Suricata 8.0.0 to 8.0.5.
- Is there a fix for CVE-2026-63452?
- A patch was published on 2026-07-07: fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63452 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-63452?
- Check whether you run OISF Suricata at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The HTTP/1 parser in Suricata 8.0.0–8.0.5 limits decompression work per individual transaction but does not limit the total number of compression bombs a single flow can submit. When response-body-decompress-layer-limit is enabled, attackers can craft multiple small compressed payloads that collectively consume excessive CPU during decompression, degrading packet processing. The vulnerability is fixed in version 8.0.6 by implementing per-flow compression bomb counting.
Affected products
- OISF Suricata 8.0.0 to 8.0.5
Timeline
- 2026-09-18: disclosed
- 2026-07-07: patched: fix committed to repository
- 2026-09-18: advisory