criticalCVSS 9.6NVD status: Deferred

CVE-2024-34359

llama.cpp: llama-cpp-python is the Python bindings for llama.cpp.

Componentllama.cpp
Severitycritical (CVSS 9.6)
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Published (NVD)2024-05-14
Last modified2026-06-17
Affected versionsnot published yet, see the advisory
Fixed insee the vendor advisory
WeaknessCWE-76
CISA KEVnot listed

NVD description

llama-cpp-python is the Python bindings for llama.cpp. `llama-cpp-python` depends on class `Llama` in `llama.py` to load `.gguf` llama.cpp or Latency Machine Learning Models. The `__init__` constructor built in the `Llama` takes several parameters to configure the loading and running of the model. Other than `NUMA, LoRa settings`, `loading tokenizers,` and `hardware settings`, `__init__` also loads the `chat template` from targeted `.gguf` 's Metadata and furtherly parses it to `llama_chat_format.Jinja2ChatFormatter.to_chat_handler()` to construct the `self.chat_handler` for this model. Nevertheless, `Jinja2ChatFormatter` parse the `chat template` within the Metadate with sandbox-less `jinja2.Environment`, which is furthermore rendered in `__call__` to construct the `prompt` of interaction. This allows `jinja2` Server Side Template Injection which leads to remote code execution by a carefully constructed payload.

Does CVE-2024-34359 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for llama.cpp.
Check my stack

What to do

  • NVD lists no fixed version yet: follow the vendor advisory below and keep llama.cpp off the public internet until a fix ships.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Other llama.cpp CVEs

All llama.cpp CVEs