{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43632 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-43632 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-43632 is a critical use after free 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-43632 and fix it if it is affected.\n\nWhat it is: CVE-2026-43632 is a critical use after free 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-43632 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-43632/ (Markdown: https://insights.sbomify.com/CVE-2026-43632/index.md)","id":"CVE-2026-43632","markdown":"https://insights.sbomify.com/CVE-2026-43632/index.md","name":"CVE-2026-43632","record":{"aliases":["DEBIAN-CVE-2026-43632","GHSA-3f2h-96vw-c84x","UBUNTU-CVE-2026-43632"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"llama.cpp server","requires_auth":"none","summary":"Attackers can trigger a use-after-free in llama-server tokenization endpoints via a race condition, potentially causing crashes or code execution when idle sleep is enabled.","user_interaction":"not_required","vuln_class":"use_after_free"},"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:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-416","name":"Use After Free"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"llama.cpp builds b7492 through the latest b9060 contains a use-after-free vulnerability in llama-server affecting six tokenization endpoints (/tokenize, /detokenize, /infill, /apply-template, /rerank, and /anthropic/count_tokens) that bypass the task queue and access ctx_server.vocab directly on HTTP worker threads. Attackers can exploit a time-of-check-time-of-use race condition where the main thread destroys and frees vocab after the synchronization lock is released but before the handler finishes using it, causing a crash or potential code execution when --sleep-idle-seconds is configured.","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 b7492–b9060 Use-After-Free in Tokenization Endpoints","id":"CVE-2026-43632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"HestiaCP 1.9.0-1.9.4 Deserialization RCE via Web Terminal","id":"CVE-2026-43633"},"packages":[],"prev":{"headline":"llama.cpp b7492–b9060 Use-After-Free RCE via llama-server","id":"CVE-2026-43631"},"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 b4882–b9058 Buffer Overflow in KV Cache State Restore","id":"CVE-2026-43629","kev_date_added":null,"published":"2026-08-06"},{"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":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-08-14","vendors":["ggml-org"]},"summary":"Attackers can trigger a use-after-free in llama-server tokenization endpoints via a race condition, potentially causing crashes or code execution when idle sleep is enabled.","url":"https://insights.sbomify.com/CVE-2026-43632/"}