CVE-2026-116829 — llama.cpp b10398 before b11301 Integer Overflow in gguf_init_from_reader
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Ggml-org Llama.cpp).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | Medium | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 6.9 | CVSS 4.0 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 6.6 | CVSS 3.1 | Medium | 1.8 | 4.7 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 6.6 | CVSS 3.1 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- Affected products added · ggml-org/llama.cpp
- Record published
- CVSS changed · 6.6
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 26, 2026 – Oct 26, 2026
- 1× Official description updated · Oct 26, 2026 – Oct 26, 2026
References
6 on the record
- github.com/ggml-org/llama.cpp/pull/29384
- github.com/ggml-org/llama.cpp/commit/2149c00f4442dc59302e134a02e4c99d5f7ed9fc
- github.com/ggml-org/llama.cpp/issues/29383
- github.com/ggml-org/llama.cpp/blob/v0.5.0/ggml/src/gguf.cpp
- github.com/ggml-org/llama.cpp/releases/tag/b11301
- www.vulncheck.com/advisories/llama-cpp-b10398-before-b11301-integer-overflow-in-gguf-in
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-118375 llama.cpp b8841 before b11865 Stack-based Buffer Overflow via ggml-rpc RDMA rdma_recv() 7h
- Medium CVE-2026-116840 llama.cpp b5854 before b11275 Integer Overflow in gguf_init_from_reader 1d
- High CVE-2026-116816 llama.cpp b5899 before b10261 Heap Out-of-Bounds Write via plamo2 Tokenizer 1d
- High CVE-2024-58400 llama.cpp before b3701 Out-of-Bounds Read in llama_decode via Token IDs 1d
- Medium CVE-2025-71439 llama.cpp before b5649 Heap Out-of-Bounds Read via llama_vocab::impl::print_info 1d
- Medium CVE-2024-58399 llama.cpp before b2731 Out-of-Bounds Read via GGUF Tensor Offsets 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-116829 is "llama.cpp b10398 before b11301 Integer Overflow in gguf_init_from_reader", rated Medium. It affects Llama.cpp (Ggml-org); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.6 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.