Is CVE-2026-94083 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-94083 being exploited in the wild.

How severe is CVE-2026-94083?

Critical severity, with a CVSS score of 9.4, published 20 September 2026.

Is there a fix for CVE-2026-94083?

A patch was published on 2026-09-15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-94083 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-94083?

Check whether you run OISF Suricata at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-94083: Suricata DoH2 type confusion in HTTP state cleanup

CVE-2026-94083 · Severity: critical · CVSS 9.4 · Published 2026-09-20

Suricata, an open-source network threat detection engine used to monitor and filter traffic on corporate networks, contains a memory corruption flaw in its DNS over HTTPS/2 (DoH2) handler. When a client sends a DoH2 upgrade request during an HTTP/1 to HTTP/2 connection upgrade, the cleanup code incorrectly frees the wrong protocol state, causing a crash or potential code execution. The vulnerability affects default configurations in Suricata 8.x.

Technologies: OISF Suricata. Vendors: OISF.

Quick answers

Is CVE-2026-94083 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-94083 being exploited in the wild.
How severe is CVE-2026-94083?: Critical severity, with a CVSS score of 9.4, published 20 September 2026.
Which products and versions are affected?: OISF Suricata before 8.0.7.
Is there a fix for CVE-2026-94083?: A patch was published on 2026-09-15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-94083 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-94083?: Check whether you run OISF Suricata at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

Type confusion in DoH2 protocol upgrade handling occurs when SCAppLayerForceProtocolChange fails to account for in-progress HTTP1-to-HTTP2 state transitions, causing the HTTP1 state to be freed prematurely before the HTTP2 cleanup runs. The vulnerability is triggered by network-supplied packets sent to a Suricata IDS/IPS instance with DoH2 support enabled (default in 8.x) and requires no authentication. Successful exploitation can lead to invalid memory free, process crash, or remote code execution depending on memory layout.

Affected products

OISF Suricata before 8.0.7

Timeline

2026-09-20: disclosed
2026-09-15: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.