{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43629 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-43629 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-43629 is a critical memory corruption vulnerability in ggml-org llama.cpp, published on 6 Aug 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-43629 and fix it if it is affected.\n\nWhat it is: CVE-2026-43629 is a critical memory corruption vulnerability in ggml-org llama.cpp, published on 6 Aug 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-43629 in the wild and no public exploit code.\n\nAffected product: ggml-org llama.cpp. 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-43629/ (Markdown: https://insights.sbomify.com/CVE-2026-43629/index.md)","id":"CVE-2026-43629","markdown":"https://insights.sbomify.com/CVE-2026-43629/index.md","name":"CVE-2026-43629","record":{"aliases":["DEBIAN-CVE-2026-43629","GHSA-7p8h-8h8j-472c","UBUNTU-CVE-2026-43629"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"LLM inference library","requires_auth":"none","summary":"Attackers with write access to state directories can trigger heap overflows in llama.cpp, potentially leading to arbitrary code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"llama.cpp","vendor":"ggml"}],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"llama.cpp builds b4882 through b9058 contain a heap buffer overflow vulnerability in the KV cache state restore path where the state_read_data() function computes write size without overflow checking, allowing attackers with write access to the slot_save_path directory to corrupt heap memory. Attackers can craft malicious state files where cell_count multiplication overflows or exceeds tensor buffer allocation to write attacker-controlled bytes past buffer boundaries, potentially resulting in heap metadata corruption, model weight corruption, or arbitrary code execution via function pointer overwrite.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"llama.cpp b4882–b9058 Buffer Overflow in KV Cache State Restore","id":"CVE-2026-43629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"llama.cpp b4882-b8487 Out-of-Bounds Read Information Disclosure","id":"CVE-2026-43630"},"packages":[],"prev":{"headline":"llama.cpp b3978–b9058 Integer Underflow via DRY Sampler","id":"CVE-2026-43628"},"products":["llama.cpp"],"published":"2026-08-06","related":[{"cvss_score":10,"headline":"llama.cpp allows write-what-where in rpc_server::set_tensor","id":"CVE-2024-42479","kev_date_added":null,"published":"2024-08-12"},{"cvss_score":9.8,"headline":"llama.cpp: Unauthenticated RCE via GRAPH_COMPUTE buffer=0 bypass in llama.cpp RPC backend","id":"CVE-2026-34159","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":9.2,"headline":"llama.cpp b7492–b9060 Use-After-Free RCE via llama-server","id":"CVE-2026-43631","kev_date_added":null,"published":"2026-08-06"},{"cvss_score":9.2,"headline":"llama.cpp b7492–b9060 Use-After-Free in Tokenization Endpoints","id":"CVE-2026-43632","kev_date_added":null,"published":"2026-08-06"},{"cvss_score":8.8,"headline":"llama.cpp has Out-of-bounds Write in llama-server","id":"CVE-2026-21869","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":8.8,"headline":"llama.cpp Vulnerable to Buffer Overflow via Malicious GGUF Model","id":"CVE-2025-49847","kev_date_added":null,"published":"2025-06-17"}],"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":"total"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["ggml-org"]},"summary":"Attackers with write access to state directories can trigger heap overflows in llama.cpp, potentially leading to arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2026-43629/"}