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.
CVE-2026-94083
CRITICALPre-NVD 9.49.4
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.4
- EG Score
- 9.4(low)
- EG Risk
- 47(Track)EG Risk 47/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity94% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 20, 2026
Last Modified
September 20, 2026
Advisory Details (3)
Auto-updated Sep 20, 2026Patch available. Sources: github_commit.
generic
Comparing suricata-8.0.6...suricata-8.0.7 · OISF/suricata · GitHub
https://github.com/OISF/suricata/compare/suricata-8.0.6...suricata-8.0.7github_commit Patch Available
commit e574009add9c (OISF/suricata)
Patch available: OISF/suricata suricata-8.0.7 (contains commit e574009add9c)
https://github.com/OISF/suricata/commit/e574009add9c208f319e1d9d15b3bb1229c88074generic
Suricata 8.0.7 released! - Announcements - Suricata
https://forum.suricata.io/t/suricata-8-0-7-released/6467Vendor Advisories for CVE-2026-94083(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 02:25 UTCEG score recompute
- 2026-09-20 01:31 UTCEG score recompute
- 2026-09-20 01:30 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-843
- CVE-2010-2299EG 10.0HIGH
- CVE-2016-1000005EG 9.8CRITICAL
- CVE-2018-4920NVD 8.8EG 9.8EPSS p94CRITICAL
- CVE-2016-6992NVD 8.8EG 9.8EPSS p93CRITICAL
- CVE-2012-0507EG 9.8 KEVEPSS p100CRITICAL
- CVE-2012-0752EG 9.3EPSS p95HIGH
- CVE-2017-5070NVD 8.8EG 9.0 KEVEPSS p98CRITICAL
- CVE-2017-11292NVD 8.8EG 9.0 KEVEPSS p96CRITICAL
- CVE-2017-8291NVD 7.8EG 9.0 KEVEPSS p100CRITICAL
- CVE-2017-0037NVD 8.1EG 9.0 KEVEPSS p100CRITICAL
Frequently asked(4)
What is CVE-2026-94083?
CVE-2026-94083 is a critical vulnerability published on September 20, 2026. 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…
When was CVE-2026-94083 disclosed?
CVE-2026-94083 was first published in the National Vulnerability Database on September 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-94083?
CVE-2026-94083 has a CVSS v3 base score of 9.4 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-94083?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-94083, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-94083
Is Your Infrastructure Affected by CVE-2026-94083?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.