Suricata smb: some SMB flows can cause resource exhaustion

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.

Scores

EPSS (exploitation in 30 days)

0.45% · top 61% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.9.

Weakness

• CWE-400: Uncontrolled Resource Consumption (opens in a new tab)All about CWE-400 and its CVEs
• CWE-401: Missing Release of Memory after Effective Lifetime (opens in a new tab)All about CWE-401 and its CVEs
• CWE-407: Inefficient Algorithmic Complexity (opens in a new tab)All about CWE-407 and its CVEs

Affected products

• OISF · suricata

  • affected >= 8.0.0, < 8.0.6
  • affected < 7.0.17

References (10)

• https://github.com/OISF/suricata/security/advisories/GHSA-hvvj-c8xx-9g35 (opens in a new tab)x_refsource_CONFIRM
• https://github.com/OISF/suricata/commit/755d6c3061de4d7ba97f0ed31cdc17ab8cab4476 (opens in a new tab)x_refsource_MISC
• https://github.com/OISF/suricata/commit/7ec9d72d28b9370712cf77a5b9d40d6b5db27cb4 (opens in a new tab)x_refsource_MISC
• https://github.com/OISF/suricata/commit/88adab8bd3d62912941647ab65032d5ec75c893a (opens in a new tab)x_refsource_MISC
• https://github.com/OISF/suricata/commit/9a54a043516e644bb7b9d34117a91977f950a281 (opens in a new tab)x_refsource_MISC
• https://github.com/OISF/suricata/commit/bc39274a638d1cca2391cfa4891c8b6c255ff9ce (opens in a new tab)x_refsource_MISC
• https://github.com/OISF/suricata/commit/c8f68b0e4f9e721dca1c9ed6e08597c6964c7ac3 (opens in a new tab)x_refsource_MISC
• https://github.com/OISF/suricata/releases/tag/suricata-7.0.17 (opens in a new tab)x_refsource_MISC
• https://github.com/OISF/suricata/releases/tag/suricata-8.0.6 (opens in a new tab)x_refsource_MISC
• https://redmine.openinfosecfoundation.org/issues/8629 (opens in a new tab)x_refsource_MISC

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-63448](https://trackcve.app/badge/CVE-2026-63448.svg)](https://trackcve.app/cve/CVE-2026-63448)

Record last updated 22 Sept 2026, 15:48 UTC.