{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64330 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-64330 is a high-severity memory corruption vulnerability in Oisf Suricata, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64330 and fix it if it is affected.\n\nWhat it is: CVE-2025-64330 is a high-severity memory corruption vulnerability in Oisf Suricata, published on 26 Nov 2025. 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-2025-64330 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-2025-64330/ (Markdown: https://insights.sbomify.com/CVE-2025-64330/index.md)","id":"CVE-2025-64330","markdown":"https://insights.sbomify.com/CVE-2025-64330/index.md","name":"CVE-2025-64330","record":{"aliases":["DEBIAN-CVE-2025-64330","GHSA-83v7-gm34-f437","UBUNTU-CVE-2025-64330"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Network IDS/IPS engine","requires_auth":"none","summary":"A heap buffer overflow in Suricata can cause crashes when logging verdicts under specific alert queue conditions, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"suricata","vendor":"oisf"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, a single byte read heap overflow when logging the verdict in eve.alert and eve.drop records can lead to crashes. This requires the per packet alert queue to be filled with alerts and then followed by a pass rule. This issue has been patched in versions 7.0.13 and 8.0.2. To reduce the likelihood of this issue occurring, the alert queue size a should be increased (packet-alert-max in suricata.yaml) if verdict is enabled.","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 is vulnerable to a heap buffer overflow on verdict","id":"CVE-2025-64330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oisf:suricata","products":["oisf:suricata"],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Suricata is vulnerable to a stack overflow on large file transfers with http-body-printable","id":"CVE-2025-64331"},"packages":[],"prev":{"headline":"containerd CRI server: Host memory exhaustion through Attach goroutine leak","id":"CVE-2025-64329"},"products":["suricata"],"published":"2025-11-26","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-28","vendors":["OISF"]},"summary":"A heap buffer overflow in Suricata can cause crashes when logging verdicts under specific alert queue conditions, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2025-64330/"}