CVE-2026-116816
Received Received - Intake

Heap Out-of-Bounds Write in llama.cpp GGUF Model Loading

Vulnerability report for CVE-2026-116816, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-27

Last updated on: 2026-10-27

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-27
Last Modified
2026-10-27
Generated
2026-10-27
AI Q&A
2026-10-27
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
ggml-org llama.cpp b5899

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-129 The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a heap out-of-bounds write issue in the PLaMo-2 tokenizer of the llama.cpp library. It occurs when parsing byte tokens in GGUF models. The function `llm_tokenizer_plamo2::build` converts hex strings to integers without validating the range. Attackers can craft tokens like <0x-1> to write before the bytes_ buffer, causing heap corruption. This leads to crashes or potential code execution during model loading.

Detection Guidance

Detecting this vulnerability requires checking the version of llama.cpp in use. Run: `llama-server --version` or inspect the installed package version. If the version is between b5899 and b10260, the system is vulnerable. Additionally, monitor for crashes during model loading, especially with GGUF files.

Impact Analysis

If you use vulnerable versions of llama.cpp (b5899 to b10260), loading a malicious GGUF model could crash your application or allow arbitrary code execution. This could compromise system integrity, confidentiality, or availability. The attack requires only loading a crafted model, which may come from public model registries.

Mitigation Strategies

Upgrade llama.cpp to version b10261 or later. This can be done via package managers or by compiling from source. Avoid loading untrusted GGUF models until the update is applied. Remove or quarantine any suspicious models that may trigger the vulnerability.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-116816. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart