{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21869 exists.","fix":"No fix published yet.","what":"CVE-2026-21869 is a high-severity memory corruption vulnerability in ggml-org llama.cpp, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-21869 and fix it if it is affected.\n\nWhat it is: CVE-2026-21869 is a high-severity memory corruption vulnerability in ggml-org llama.cpp, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21869 exists.\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-21869/ (Markdown: https://insights.sbomify.com/CVE-2026-21869/index.md)","id":"CVE-2026-21869","markdown":"https://insights.sbomify.com/CVE-2026-21869/index.md","name":"CVE-2026-21869","record":{"aliases":["DEBIAN-CVE-2026-21869","GHSA-8947-pfff-2f3c","UBUNTU-CVE-2026-21869","openSUSE-SU-2026:10961-1"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"LLM inference server","requires_auth":"none","summary":"Attackers can trigger out-of-bounds writes via negative parameters in llama.cpp server, potentially causing crashes or remote code execution.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"llama.cpp","vendor":"ggml"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"llama.cpp is an inference of several LLM models in C/C++. In commits 55d4206c8 and prior, the n_discard parameter is parsed directly from JSON input in the llama.cpp server's completion endpoints without validation to ensure it's non-negative. When a negative value is supplied and the context fills up, llama_memory_seq_rm/add receives a reversed range and negative offset, causing out-of-bounds memory writes in the token evaluation loop. This deterministic memory corruption can crash the process or enable remote code execution (RCE). There is no fix at the time of publication.","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"llama.cpp has Out-of-bounds Write in llama-server","id":"CVE-2026-21869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"The BACnet Protocol Stack library has an Off-by-one Stack-based Buffer Overflow in tokenizer_string","id":"CVE-2026-21870"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["9500-1.1"],"introduced":["0"],"last_affected":[],"package":"llamacpp","purl":"pkg:rpm/opensuse/llamacpp\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:10961-1"}],"prev":{"headline":"Flag Forge has ReDoS Vulnerability in User Profile Lookup API","id":"CVE-2026-21868"},"products":["llama.cpp"],"published":"2026-01-07","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":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 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":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-08","vendors":["ggml-org"]},"summary":"Attackers can trigger out-of-bounds writes via negative parameters in llama.cpp server, potentially causing crashes or remote code execution.","url":"https://insights.sbomify.com/CVE-2026-21869/"}