CISA ADP Vulnrichment

Answer in brief

CVE-2026-94083 records a Critical severity (CVSS 9.4) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps OISF/Suricata (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 20, 2026Updated Sep 22, 2026Source checked Sep 22, 2026First seen by HOL Sep 20, 2026Material review Sep 22, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.4
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 9.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OISF/Suricata (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
OISF/Suricatageneric	>=8.0.0 <8.0.7	8.0.7

Recommended response

Check inventory. Check lockfiles and deployed manifests for OISF/Suricata.
Review the reported fix. Update OISF/Suricata to 8.0.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 20, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.