Live › vulnerability › CVE-2026-116840
Go to dashboardllama.cpp's GGUF model loader has an integer overflow in gguf_init_from_reader that skips an earlier size check when tensor sizes are near the maximum value. A crafted GGUF file can make the tensor data blob undersized, so consumers read past the end of the buffer.
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 builds from b5854 up to but not including b11275 and load GGUF model files, especially files they did not produce themselves. Systems that only load models they built or downloaded from a vetted source are less exposed. Teams on builds outside this range can skip it.
No product ranges from the sources yet.
llama-cli --version or check the build tag and confirm it is b5854 or later but before b11275b11275 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
llama.cpp b5854 before b11275 contains an integer overflow vulnerability in gguf_init_from_reader that bypasses the CVE-2025-53630 size check when padding near-SIZE_MAX tensor sizes. Attackers can supply a crafted GGUF file whose tensor size pads to zero, causing an undersized data blob and out-of-bounds reads by consumers.
This page as .md · .json · in your agent: get_signal("CVE-2026-116840")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.