CVSS 3.1
9.4 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:LCritical (9.4) in oisf suricata. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:LExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| OISF Suricata | from 8.0.0 before 8.0.7 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | suricata | no fix listed | DEBIAN-CVE-2026-94083 |
| Debian | 14 | suricata | 1:8.0.7-1 | DEBIAN-CVE-2026-94083 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 22.04:LTS and 3 more | suricata | no fix listed | UBUNTU-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 rates this Critical.
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.
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.