Monitoring disruption via repeated Brotli decompression
Published Sep 18, 2026 · Updated Sep 18, 2026
Resource exhaustion in Suricata 8.0.0 through 8.0.5 allows remote attackers to degrade packet processing with crafted HTTP/1 traffic. The rust/htp parser limits decompression work per transaction but repeatedly decompresses small Brotli bombs because it lacks a per-flow bomb-count limit. The response-body-decompress-layer-limit setting must be enabled, and sustained processing can interrupt monitoring or cause denial of service.
Summary
What happened
Resource exhaustion in Suricata 8.0.0 through 8.0.5 allows remote attackers to degrade packet processing with crafted HTTP/1 traffic. The rust/htp parser limits decompression work per transaction but repeatedly decompresses small Brotli bombs because it lacks a per-flow bomb-count limit. The response-body-decompress-layer-limit setting must be enabled, and sustained processing can interrupt monitoring or cause denial of service.
The record
- CVE
- CVE-2026-63452
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- Open Information Security Foundation
- Product
- Suricata
- Classifications
- CWE-409, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=>= 8.0.0, < 8.0.6
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.
Weakness, pattern, technique
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