Suricata app-layer: passed flows can retain transactions, causing resource exhaustion
cve-program · CVE-2026-63446
PublishedSuricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. From 8.0.0 until 8.0.6, AppLayerParserSetTransactionInspectId() in src/app-layer-parser.c uses an inverted guard and marks only already-inspected transactions as inspected. On flows passed by a pass rule or pass-the-flow exception policy, detection is skipped, so completed transactions remain unmarked, are never freed, and are repeatedly rescanned. The per-flow list can grow without bound with quadratic cleanup cost, causing CPU and memory exhaustion. This issue is fixed in version 8.0.6.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-63446 · CVE overview and exploitation status
cve-program · CVE-2026-63446
- https://github.com/OISF/suricata/security/advisories/GHSA-gjwr-75gq-877m
- https://github.com/OISF/suricata/pull/15726
- https://github.com/OISF/suricata/commit/006e21c1ccc38c1c815e7945d54b4638cc5f0de8
- https://github.com/OISF/suricata/commit/60a83c62a1dfdfb589b2bad27fb7fc339fc964b7
- https://github.com/OISF/suricata/releases/tag/suricata-8.0.6
- https://redmine.openinfosecfoundation.org/issues/8628
Related changes
Linked by CVE identifierNo related changes are available here.