Skip to main content
VulnerabilityPublished Updated

CVE-2026-71418: OISF suricata · Inefficient Algorithmic Complexity

Affects OISF suricataSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 8.0.6 soon.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.0.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade suricata and oisf/suricata to 8.0.6.

Affected software

ProductAffectedFixed in
OISFsuricataAffected
  • >=8.0.0 <8.0.6
Fixed in
  • 8.0.6
GitHuboisf/suricatapkg:github/oisf/suricataOther threatsAffected
  • >=8.0.0 <8.0.6
Fixed in
  • 8.0.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Suricata version 8.0.6. Users should upgrade to version 8.0.6 or later to remediate this vulnerability. No other mitigation or workaround is indicated.

Description

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. From 8.0.0 until 8.0.6, DNS-over-HTTP/2 processing in rust/src/http2/http2.rs retains previously processed HTTP/2 DATA frame contents instead of clearing the internal buffer. Multiple DATA frames with the EndOfStream flag set can grow the buffer to its 65 KiB limit while causing all prior contents to be processed again, producing quadratic CPU complexity, degraded packet processing, loss of monitoring visibility, or denial of service. This issue is fixed in version 8.0.6.

References

Community reviews

Loading reviews…