CVE-2026-45752: OISF suricata · Use After Free
Affects OISF suricataSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.0.5 when convenient.
Data as of 26 Oct 2026, 12:29 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.0.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade suricata and oisf/suricata to 8.0.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OISFsuricata | Affected
| Fixed in
|
GitHuboisf/suricatapkg:github/oisf/suricataOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Suricata to version 8.0.5 or later, which contains an official fix for this vulnerability. As a temporary workaround, avoid using detection rules that chain 'gunzip' or 'zlib_deflate' transforms with a max-size greater than 4096 after another transform. No other mitigation steps are indicated.
Description
CVE-2026-45752 is a use-after-free vulnerability in Suricata versions 8.0.0 up to but not including 8.0.5. It occurs when certain detection transforms are chained, causing the decompress transform pipeline to read from a buffer after it has been freed. This flaw can cause Suricata to crash during network traffic processing if a malicious rule triggers it. Version 8.0.5 includes a fix for this issue. A temporary workaround is to avoid rules chaining 'gunzip' or 'zlib_deflate' with a max-size greater than 4096 after another transform.