llama.cppPublished 27 Oct 2026NVD status: Awaiting Analysis

CVE-2026-116840

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.

Componentllama.cpp
Severitymedium (CVSS 6.1)
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
Published (NVD)2026-10-27
Affected versions
>= b5854, < b11275
>= 0.1.0, < 0.6.0
from the CVE Program record written by the CNA that assigned the CVE
Fixed inb11275, 0.6.0
WeaknessCWE-190
CISA KEVnot listed

Versions, checked against NVD

NVD's record (status: Awaiting Analysis) lists no affected versions of llama.cpp for this CVE. The ranges above come from the CVE record written by VulnCheck, the CNA that assigned the CVE.

NVD description

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.

What to do

  • Upgrade llama.cpp to the fixed release of the branch you run: b11275 or 0.6.0, or later.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources