# CVE-2026-116829: llama.cpp b10398 before b11301 Integer Overflow in gguf_init_from_reader


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116829, GHSA-3jhp-qv93-3428, UBUNTU-CVE-2026-116829

## What is CVE-2026-116829?

CVE-2026-116829 is a medium-severity vulnerability in ggml-org llama.cpp, published on 27 Oct 2026. 

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-116829?


## How do I fix CVE-2026-116829?

Upgrade to a fixed version.

## Is CVE-2026-116829 being exploited?

There is no known exploitation of CVE-2026-116829 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116829 and fix it if it is affected.

What it is: CVE-2026-116829 is a medium-severity vulnerability in ggml-org llama.cpp, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116829 in the wild and no public exploit code.

Affected product: ggml-org llama.cpp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116829/ (Markdown: https://insights.sbomify.com/CVE-2026-116829/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116829
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116829
- OSV: https://osv.dev/vulnerability/CVE-2026-116829

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116829/
Summaries are generated and may contain mistakes; the official description above is the record.