{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-63448 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-63448 is a medium-severity denial of service vulnerability in Oisf Suricata, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63448 and fix it if it is affected.\n\nWhat it is: CVE-2026-63448 is a medium-severity denial of service vulnerability in Oisf Suricata, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63448 in the wild and no public exploit code.\n\nAffected product: Oisf Suricata. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63448/ (Markdown: https://insights.sbomify.com/CVE-2026-63448/index.md)","id":"CVE-2026-63448","markdown":"https://insights.sbomify.com/CVE-2026-63448/index.md","name":"CVE-2026-63448","record":{"aliases":["DEBIAN-CVE-2026-63448","GHSA-hvvj-c8xx-9g35","UBUNTU-CVE-2026-63448"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Network IDS/IPS","requires_auth":"none","summary":"Attackers can cause resource exhaustion in Suricata by sending sustained one-directional SMB traffic, leading to CPU and memory depletion.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"suricata","vendor":"oisf"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"},{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Suricata smb: some SMB flows can cause resource exhaustion","id":"CVE-2026-63448","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oisf:suricata","products":["oisf:suricata"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Suricata sip: large SIP message bodies can evade detection with frame keyword","id":"CVE-2026-63449"},"packages":[],"prev":{"headline":"Suricata ftp: crafted FTP traffic can cause quadratic CPU consumption","id":"CVE-2026-63447"},"products":["suricata"],"published":"2026-09-18","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-35853","kev_date_added":null,"published":"2023-06-19"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2021-37592","kev_date_added":null,"published":"2021-11-19"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2018-10244","kev_date_added":null,"published":"2019-04-04"},{"cvss_score":9.4,"headline":"Memory corruption in Suricata","id":"CVE-2026-94083","kev_date_added":null,"published":"2026-09-20"},{"cvss_score":9.4,"headline":"Use after free in Suricata","id":"CVE-2026-94084","kev_date_added":null,"published":"2026-09-20"},{"cvss_score":9.1,"headline":"Suricata http2: protocol-change type confusion can lead to denial of service","id":"CVE-2026-45764","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":8.2,"headline":"Suricata smtp/mime: heap out-of-bounds read quoted-printable decoder","id":"CVE-2026-57228","kev_date_added":null,"published":"2026-09-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["OISF"]},"summary":"Attackers can cause resource exhaustion in Suricata by sending sustained one-directional SMB traffic, leading to CPU and memory depletion.","url":"https://insights.sbomify.com/CVE-2026-63448/"}