cve.bz

CVE-2026-94083 oisf suricata: Type Confusion

9.4 criticalEPSS 0.5%Fix available

Critical (9.4) in oisf suricata. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
Suricata before 8.0.7 has a DoH2 type confusion that can cause an invalid free, because cleanup code for the HTTP2 state is executed even though the actual state is HTTP1 (when there is a DoH2 request with an HTTP1 to HTTP2 upgrade). This requires app-layer.protocols.doh2 to be enabled, which is the default in 8.x versions.

Severity

CVSS 3.1

9.4 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-09-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-843 Access of Resource Using Incompatible Type (Type Confusion)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-94083 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-94083?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-94083?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-94083 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OISF Suricatafrom 8.0.0 before 8.0.7

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13suricatano fix listedDEBIAN-CVE-2026-94083
Debian14suricata1:8.0.7-1DEBIAN-CVE-2026-94083
Ubuntu16.04:LTS, 18.04:LTS, 22.04:LTS and 3 moresuricatano fix listedUBUNTU-CVE-2026-94083

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

A flaw was found in Suricata's DNS over HTTPS 2 (DoH2) application-layer protocol handler. When processing a DoH2 request accompanied by an HTTP/1 to HTTP/2 connection upgrade, Suricata incorrectly executes HTTP/2 state cleanup logic while in an HTTP/1 state. This type confusion triggers an invalid memory free, which a remote, unauthenticated attacker can exploit by sending crafted protocol upgrade traffic to crash the Suricata daemon or potentially execute arbitrary code with the privileges of the Suricata process.

Red Hat's mitigation

Disable the DNS over HTTPS 2 protocol handler by setting `app-layer.protocols.doh2.enabled: false` in `/etc/suricata/suricata.yaml` and restart the Suricata service.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-94083.

References

Check your stackJSON