llama.cpp b5899 before b10261 Heap Out-of-Bounds Write via plamo2 Tokenizer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in b10261
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
llama.cpp, an open-source library for running large language models, is affected by this vulnerability in its PLaMo-2 tokenizer. A maliciously crafted GGUF model file can corrupt memory while loading, which could crash the software or potentially allow an attacker to run arbitrary code.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
llama.cpp b5899 before b10261 contains a heap out-of-bounds write vulnerability in llm_tokenizer_plamo2::build that allows attackers to corrupt heap memory via crafted GGUF models. Attackers can supply BYTE-typed token text like <0x-1> whose negative parsed value writes token ids before the bytes_ buffer during model loading, causing crashes or potential code execution.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ggml-org llama.cpp
From b5899 · fixed in b10261