Skip to content
major vulnerability· requires attention

Suricata is a widely deployed network IDS/IPS; default DoH2 setting is affected. Exploitation can disrupt or compromise detection infrastructure across organizations.

Networks

CVE-2026-94083

9.4
Critical
EPSS n/aPatch availableSep 21, 2026

Suricata DoH2 type-confusion allows crash or potential RCE via HTTP1->HTTP2 upgrade

common questions

Is CVE-2026-94083 being exploited?

Not confirmed. CVE-2026-94083 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-94083?

CVE-2026-94083 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-94083?

Yes. A fix has been recorded for CVE-2026-94083. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-94083 affect?

CVE-2026-94083 affects OISF Suricata < 8.0.7, Suricata 8.x with app-layer.protocols.doh2 enabled, IDS/IPS appliances embedding Suricata. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-94083?

Upgrade to Suricata 8.0.7+ or disable app-layer.protocols.doh2 until patched

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OISF Suricata < 8.0.7Suricata 8.x with app-layer.protocols.doh2 enabledIDS/IPS appliances embedding Suricata
impact

Remote memory corruption via crafted DoH2 (HTTP1->HTTP2 upgrade) can crash Suricata (DoS) or enable arbitrary code execution.

action required

Immediate action required

affected versions
OISF Suricata
  • affected>= 8.0.0 and < 8.0.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free