Live › vulnerability › CVE-2026-116829
Go to dashboardllama.cpp builds before b11301 fail to validate tensor element counts when loading GGUF model files, so a crafted shape can wrap to zero and bypass the check. Buffers are then sized from the wrapped byte counts, which lets an attacker cause out-of-bounds memory access when the file is loaded.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 01:34 UTC. All times on this page are UTC.
Teams that run llama.cpp, or products that embed it, and load GGUF model files. The risk is greatest where users or external parties can supply the model file. Teams that only load models they built or vetted themselves are lower risk, though the upgrade still applies.
No product ranges from the sources yet.
llama-cli --version or check the build tag of the llama.cpp binary in use; builds from b10398 up to but not including b11301 are listed as affected.b11301 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
llama.cpp b10398 before b11301 contains an integer overflow vulnerability in gguf_init_from_reader that allows attackers to bypass tensor element-count validation by supplying shapes whose product wraps to zero. Attackers can craft GGUF files with enormous tensor extents that overflow ggml_nbytes() and strides, causing out-of-bounds memory access when buffers are sized from wrapped byte counts.
This page as .md · .json · in your agent: get_signal("CVE-2026-116829")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.