CVE-2026-63448: OISF suricata · Uncontrolled Resource Consumption
Affects OISF suricataSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.0.6 or 7.0.17 when convenient.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.0.6, 7.0.17
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade suricata and oisf/suricata to 8.0.6 or 7.0.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OISFsuricata | Affected
| Fixed in
|
| OISFsuricata | Affected
| Fixed in
|
GitHuboisf/suricatapkg:github/oisf/suricataOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Suricata to version 7.0.17 or later, or 8.0.6 or later, where this issue is fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed fixed in these versions.
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, the SMB parser can retain force-completed transactions on flows where Suricata sees payload in only one direction, including async-oneside flows, because cleanup waits for inspection in the unseen direction. The transaction creation paths in rust/src/smb can exceed the intended SMB_MAX_TX bound, and cleanup repeatedly scans the growing list. Sustained one-directional SMB traffic can therefore cause unbounded per-flow state and CPU and memory exhaustion. This issue is fixed in versions 8.0.6 and 7.0.17.
References
- github.com/OISF/suricata/security/advisories/GHSA-hvvj-c8xx-9g35 (opens in a new tab)
- github.com/OISF/suricata/commit/755d6c3061de4d7ba97f0ed31cdc17ab8cab4476 (opens in a new tab)
- github.com/OISF/suricata/commit/7ec9d72d28b9370712cf77a5b9d40d6b5db27cb4 (opens in a new tab)
- github.com/OISF/suricata/commit/88adab8bd3d62912941647ab65032d5ec75c893a (opens in a new tab)
- github.com/OISF/suricata/commit/9a54a043516e644bb7b9d34117a91977f950a281 (opens in a new tab)
- github.com/OISF/suricata/commit/bc39274a638d1cca2391cfa4891c8b6c255ff9ce (opens in a new tab)
- github.com/OISF/suricata/commit/c8f68b0e4f9e721dca1c9ed6e08597c6964c7ac3 (opens in a new tab)
- github.com/OISF/suricata/releases/tag/suricata-7.0.17 (opens in a new tab)
- github.com/OISF/suricata/releases/tag/suricata-8.0.6 (opens in a new tab)
- redmine.openinfosecfoundation.org/issues/8629 (opens in a new tab)