CVE-2026-45764: OISF suricata · Type Confusion
Affects OISF suricataSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 8.0.5 or 7.0.16 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.0.5, 7.0.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 2026-10-25.
What to do
Upgrade suricata and oisf/suricata to 8.0.5 or 7.0.16.
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 7.0.16 or 8.0.5 or later, where the vulnerability is fixed. If upgrading is not immediately possible, disable HTTP/2 parsing as a temporary workaround to prevent exploitation of this issue.
Description
CVE-2026-45764 is a critical vulnerability in Suricata, a network intrusion detection and prevention system. The flaw involves a type confusion issue triggered by a protocol change while processing HTTP/2 traffic. This can cause Suricata to crash, resulting in a denial of service. Versions prior to 7.0.16 and 8.0.5 are affected. Fixed versions 7.0.16 and 8.0.5 address this issue. Disabling HTTP/2 parsing is a recommended workaround if that functionality is not needed.