Suricata 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.
CVE-2026-63446
HIGHPre-NVD 7.57.5
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (6)
Auto-updated Sep 18, 2026Patch available. Sources: github_commit, github_release, github, github_pr.
github_release Patch Available
8.0.6
Patch available: OISF/suricata suricata-8.0.6
https://github.com/OISF/suricata/releases/tag/suricata-8.0.6github_commit Patch Available
commit 60a83c62a1df (OISF/suricata)
Patch available: OISF/suricata suricata-8.0.6 (contains commit 60a83c62a1df)
https://github.com/OISF/suricata/commit/60a83c62a1dfdfb589b2bad27fb7fc339fc964b7github_commit
commit 006e21c1ccc3 (OISF/suricata)
Fix landed in OISF/suricata commit 006e21c1ccc3 — awaiting tagged release
https://github.com/OISF/suricata/commit/006e21c1ccc38c1c815e7945d54b4638cc5f0de8github_pr
next/1407/20260624/v1
Fix merged in OISF/suricata PR #15726 on 2026-06-25 — awaiting tagged release
https://github.com/OISF/suricata/pull/15726github Patch Available
app-layer: passed flows can retain transactions, causing resource exhaustion · Advisory · OISF/suricata · GitHub
https://github.com/OISF/suricata/security/advisories/GHSA-gjwr-75gq-877mWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 21:17 UTCEG score recompute
- 2026-09-18 20:25 UTCEG score recompute
- 2026-09-18 20:24 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-63446?
CVE-2026-63446 is a high vulnerability published on September 18, 2026. Suricata 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…
When was CVE-2026-63446 disclosed?
CVE-2026-63446 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-63446?
CVE-2026-63446 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-63446?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63446, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63446
Is Your Infrastructure Affected by CVE-2026-63446?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.