CVE-2026-94083: OISF Suricata · Type Confusion
Affects OISF SuricataSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical : upgrade to 8.0.7 as a priority.
Data as of 3 Nov 2026, 22:58 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.0.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 3 Nov 2026.
What to do
Upgrade Suricata and oisf/suricata to 8.0.7.
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.7 or later, where this type confusion vulnerability is fixed. Since this is an official fix, applying the update fully mitigates the issue. If upgrading immediately is not possible, consider disabling the app-layer.protocols.doh2 feature as a temporary workaround, though this may impact functionality. Patch status is confirmed fixed in 8.0.7.
Description
CVE-2026-94083 is a critical type confusion vulnerability in Suricata before version 8.0.7. It occurs in the handling of DNS over HTTPS version 2 (DoH2) requests when the HTTP1 to HTTP2 upgrade is involved, causing cleanup code for HTTP2 state to run incorrectly on HTTP1 state. This can lead to an invalid free operation, potentially causing a denial of service. The vulnerability requires the app-layer.protocols.doh2 feature to be enabled, which is the default in Suricata 8.x versions.