Skip to content
major vulnerability· requires attention

Suricata is widely deployed as core IDS/IPS; a high-severity UAF enabling RCE/DoS in traffic inspection impacts many orgs' network defenses.

Networks

CVE-2026-94084

9.4
Critical
EPSS n/aPatch availableSep 21, 2026

Use-after-free in Suricata HTTP/2 processing enabling crash or possible RCE

common questions

Is CVE-2026-94084 being exploited?

Not confirmed. CVE-2026-94084 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-94084?

CVE-2026-94084 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-94084?

Yes. A fix has been recorded for CVE-2026-94084. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-94084 affect?

CVE-2026-94084 affects Suricata < 8.0.7, IDS/IPS appliances running Suricata, Network security sensors. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-94084?

Upgrade to Suricata 8.0.7+ immediately and restart sensors

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Suricata < 8.0.7IDS/IPS appliances running SuricataNetwork security sensors
impact

Crafted HTTP/2 traffic can trigger a use-after-free during http.response_header rule inspection, enabling remote code execution or denial of service.

action required

Immediate action required

affected versions
OISF Suricata
  • affected< 8.0.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free