CVE-2026-57222
Suricata ippair: hash collision can cause incorrect state reuse across IPv4 and IPv6
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, crafted IPv4 and IPv6 address pairs can collide in the IPPair hash because src/ippair.c did not compare the IP address family before reusing IPPair-backed state. This can apply state from one IP family to another for xbits track ip_pair, FTP data expectations, and, on the 7.0 release line, thresholding, detection_filter, and rate_filter rules using track by_both, causing incorrect detection state. This issue is fixed in versions 8.0.6 and 7.0.17.
INFO
Published Date :
Sept. 18, 2026, 8:17 p.m.
Last Modified :
Sept. 18, 2026, 8:17 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update Suricata to version 8.0.6 or later.
- Update Suricata to version 7.0.17 or later.
- Ensure IP address family is compared before state reuse.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-57222.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-57222 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-57222
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-57222 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-57222 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Sep. 18, 2026
Action Type Old Value New Value Added 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, crafted IPv4 and IPv6 address pairs can collide in the IPPair hash because src/ippair.c did not compare the IP address family before reusing IPPair-backed state. This can apply state from one IP family to another for xbits track ip_pair, FTP data expectations, and, on the 7.0 release line, thresholding, detection_filter, and rate_filter rules using track by_both, causing incorrect detection state. This issue is fixed in versions 8.0.6 and 7.0.17. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Added CWE CWE-697 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/57xxx/CVE-2026-57222.json">CVE-2026-57222</a> Added Reference https://github.com/OISF/suricata/commit/4a728464e6eb9e273bb02e3df0c28929b28db71d Added Reference https://github.com/OISF/suricata/commit/9d788575c5d22a34eeed50d56557ed12b05e0aec Added Reference https://github.com/OISF/suricata/commit/c92e270c4a795c52bce610aa1ce9ebaf065c49e6 Added Reference https://github.com/OISF/suricata/releases/tag/suricata-7.0.17 Added Reference https://github.com/OISF/suricata/releases/tag/suricata-8.0.6 Added Reference https://github.com/OISF/suricata/security/advisories/GHSA-2r8x-23fw-hgcg Added Reference https://redmine.openinfosecfoundation.org/issues/8559