Skip to main content
VulnerabilityPublished Updated

CVE-2026-71855: OISF suricata · Incorrect Comparison

Affects OISF suricataSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.0.6 or 7.0.17 when convenient.

Data as of 1 Nov 2026, 22:58 UTC

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

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 1 Nov 2026.

What to do

Upgrade suricata and oisf/suricata to 8.0.6 or 7.0.17.

Affected software

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

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

AI-suggested

This issue is fixed in Suricata versions 7.0.17 and 8.0.6. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to 7.0.17 and 8.0.6, src/flow-hash.c can treat an IPv4 and IPv6 flow as equal without comparing the IP family when their raw address words, ports, protocol, VLAN, recursion level, live device, and hash bucket align. An IPv6 packet can therefore reuse IPv4 flow state or the reverse, causing incorrect flowbit state, detection bypass, or IP-only bypass. This issue is fixed in versions 8.0.6 and 7.0.17.

References

Community reviews

Loading reviews…