UBUNTU-CVE-2026-57222 (CVE-2026-57222)
Vulnerability from osv_ubuntu – Published: 2026-09-18 20:17 – Updated: 2026-09-23 23:31 – Source websiteSuricata 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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "suricata",
"binary_version": "3.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "suricata",
"purl": "pkg:deb/ubuntu/suricata@3.0-1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.0.8-1build1",
"2.0.9-1",
"2.0.10-1",
"2.0.10-2",
"2.0.11-1",
"3.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libhtp-0.5.23-1",
"binary_version": "3.2-2ubuntu3"
},
{
"binary_name": "suricata",
"binary_version": "3.2-2ubuntu3"
},
{
"binary_name": "suricata-hyperscan",
"binary_version": "3.2-2ubuntu3"
},
{
"binary_name": "suricata-oinkmaster",
"binary_version": "3.2-2ubuntu3"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "suricata",
"purl": "pkg:deb/ubuntu/suricata@3.2-2ubuntu3?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.2-2ubuntu3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "suricata",
"binary_version": "1:6.0.4-3"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "suricata",
"purl": "pkg:deb/ubuntu/suricata@1:6.0.4-3?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:6.0.4-2",
"1:6.0.4-3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "suricata",
"binary_version": "1:7.0.3-1build3"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "suricata",
"purl": "pkg:deb/ubuntu/suricata@1:7.0.3-1build3?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:7.0.0-2",
"1:7.0.2-1",
"1:7.0.2-1build1",
"1:7.0.3-1build1",
"1:7.0.3-1build3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "suricata",
"binary_version": "1:8.0.3-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "suricata",
"purl": "pkg:deb/ubuntu/suricata@1:8.0.3-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:7.0.10-1",
"1:8.0.1-3build1",
"1:8.0.2-1",
"1:8.0.2-1build1",
"1:8.0.3-1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-57222",
"modified": "2026-09-23T23:31:24Z",
"published": "2026-09-18T20:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-57222"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-57222"
},
{
"type": "REPORT",
"url": "https://github.com/OISF/suricata/security/advisories/GHSA-2r8x-23fw-hgcg"
},
{
"type": "REPORT",
"url": "https://redmine.openinfosecfoundation.org/issues/8569"
},
{
"type": "REPORT",
"url": "https://redmine.openinfosecfoundation.org/issues/8568"
},
{
"type": "REPORT",
"url": "https://github.com/OISF/suricata/commit/9d788575c5d22a34eeed50d56557ed12b05e0aec"
},
{
"type": "REPORT",
"url": "https://github.com/OISF/suricata/commit/c92e270c4a795c52bce610aa1ce9ebaf065c49e6"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-57222"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.