{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32878 exists.","fix":"No fix has been published for CVE-2024-32878 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-32878 is a high-severity use after free vulnerability in ggerganov llama.cpp, published on 26 Apr 2024. 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-2024-32878 and fix it if it is affected.\n\nWhat it is: CVE-2024-32878 is a high-severity use after free vulnerability in ggerganov llama.cpp, published on 26 Apr 2024. 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-2024-32878 exists.\n\nAffected product: ggerganov 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-2024-32878/ (Markdown: https://insights.sbomify.com/CVE-2024-32878/index.md)","id":"CVE-2024-32878","markdown":"https://insights.sbomify.com/CVE-2024-32878/index.md","name":"CVE-2024-32878","record":{"aliases":["GHSA-p5mv-gjc5-mwqv"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LLM inference library","requires_auth":"none","summary":"Attackers can cause crashes or potentially execute arbitrary code via a crafted GGUF file due to uninitialized variable usage in llama.cpp.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"llama.cpp","vendor":"ggml"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-456","name":"Missing Initialization of a Variable"}],"description":"Llama.cpp is LLM inference in C/C++. There is a use of uninitialized heap variable vulnerability in gguf_init_from_file, the code will free this uninitialized variable later. In a simple POC, it will directly cause a crash. If the file is carefully constructed, it may be possible to control this uninitialized value and cause arbitrary address free problems. This may further lead to be exploited. Causes llama.cpp to crash (DoS) and may even lead to arbitrary code execution (RCE). This vulnerability has been patched in commit b2740.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Use of Uninitialized Variable Vulnerability in llama.cpp","id":"CVE-2024-32878","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"social-auth-app-django Improper Handling of Case Sensitivity vulnerability","id":"CVE-2024-32879"},"packages":[],"prev":{"headline":"Reflected Cross-site Scripting in yiisoft/yii2 Debug mode","id":"CVE-2024-32877"},"products":["llama.cpp"],"published":"2024-04-26","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 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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["ggerganov"]},"summary":"Attackers can cause crashes or potentially execute arbitrary code via a crafted GGUF file due to uninitialized variable usage in llama.cpp.","url":"https://insights.sbomify.com/CVE-2024-32878/"}