Vulnerability · 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 size
Published Oct 27, 2026 · catalog updated Oct 27, 2026 · llama.cpp b5854 before b11275
Last checked Nov 5, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-116840. EPSS is 0.13%. Act only if a listed version of llama.cpp b5854 before b11275 is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (llama.cpp b5854 before b11275).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium6.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.13%
- Remediation
- Advisory link
- Affected products
- Debian:14 llama.cpp
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Debian:14 llama.cpp0 → 1:0.6.0+dfsg-1
How to fix CVE-2026-116840
Upgrade
CVE-2026-116840 lists a fix boundary at 1:0.6.0+dfsg-1. Compare the installed build with that boundary before you change production.
Version check
Fixed in 1:0.6.0+dfsg-1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-116840. EPSS is 0.13%. Act only if a listed version of llama.cpp b5854 before b11275 is installed.
Which versions are affected?
Compare what you have installed with 0 → 1:0.6.0+dfsg-1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 27, 2026 · Trivy Vulnerability DB
Detected
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.
Oct 27, 2026 · Trivy Vulnerability DB
Fix available
llama.cpp fixed in 1:0.6.0+dfsg-1
Oct 27, 2026 · Trivy Vulnerability DB
Fix available
llama.cpp fixed in 1:0.6.0+dfsg-1
Oct 27, 2026 · Trivy Vulnerability DB
Updated
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.
Sources
- CVE.orgVulnerability recordCVE-2026-116840
Official CVE identifier
cve.org - Trivy Vulnerability DBPackage advisoryDEBIAN-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. Attackers can supply a crafted GGUF file whose tensor size pads to zero, causing an undersized da
osv.dev
References
Freshness
Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgOct 27, 2026
- Trivy Vulnerability DBOct 27, 2026