Suricata flow: IPv4/IPv6 hash collision can reuse wrong flow state
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: suricata (Debian:14) 1:8.0.6-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to suricata (Debian:14) 1:8.0.6-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 18, 2026
- Updated
- Sep 28, 2026
- EPSS
- 0.3% · 22th percentile
- CWE
- CWE-697
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 5.9
- 1.6 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| oisf | suricata | cpe:2.3:a:oisf:suricata |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- oisf suricatabefore 7.0.17
- oisf suricata8.0.0 and later · before 8.0.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
OISF suricata
- >= 8.0.0, < 8.0.6, < 7.0.17affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | suricata | from 0 | — |
| Debian:14 | suricata | before 1:8.0.6-1 | 1:8.0.6-1 |
Same product
oisf: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-22262Suricata datasets: stack overflow when saving a set39Monitor
- CVE-2023-35853In Suricata before 6.0.13, an adversary who controls an external source of Lua rules may be able to execute Lua code.39Monitor
- CVE-2021-37592Suricata before 5.0.8 and 6.x before 6.0.4 allows TCP evasion via a client with a crafted TCP/IP stack that can send a certain sequence of s39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-63452Sep 18, 2026 · Suricata http1: repeated brotli compression bombs can cause excessive CPU consumption30Monitor
- ← EarlierCVE-2026-71418Sep 18, 2026 · Suricata doh2: crafted HTTP/2 DATA frames can cause quadratic CPU consumption30Monitor
- Later →CVE-2026-94083Sep 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 th37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:suricata | 1:8.0.6-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-572220 days apartSuricata ippair: hash collision can cause incorrect state reuse across IPv4 and IPv621Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1136 · Sep 21, 2026(Suricata Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-697 · Incorrect ComparisonCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Command DelimitersCAPEC-15likelihood: High · High
- Flash InjectionCAPEC-182likelihood: High · Medium
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Leading 'Ghost' Character Sequences to Bypass Input FiltersCAPEC-3likelihood: Medium · Medium
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/OISF/suricata/commit/4e2f23d031fbcfd72883bacd3d723c9874f23701
- github.com/OISF/suricata/commit/bc41dcc854e24487d3786ce578a8a86a8350ab20
- github.com/OISF/suricata/releases/tag/suricata-7.0.17
- github.com/OISF/suricata/releases/tag/suricata-8.0.6
- github.com/OISF/suricata/security/advisories/GHSA-fvwh-wjcq-2586
- redmine.openinfosecfoundation.org/issues/8558
Vendor advisories and official records. Exploit/PoC links are deliberately left out.