# CVE-2026-116467: ggml-org llama.cpp Mirostat Sampler llama-sampler.cpp assertion


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116467, GHSA-qh3g-v296-6ghm, UBUNTU-CVE-2026-116467

## What is CVE-2026-116467?

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

### Official description

A security flaw has been discovered in ggml-org llama.cpp up to 0.7.0. Affected by this vulnerability is an unknown functionality of the file src/llama-sampler.cpp of the component Mirostat Sampler. The manipulation results in reachable assertion. It is possible to launch the attack remotely. The project was informed of the problem early through a pull request but has not reacted yet.

Weakness: CWE-617 (Reachable Assertion)

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


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

No fix has been published for CVE-2026-116467 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116467 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116467 is a medium-severity vulnerability in ggml-org llama.cpp, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116467 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-116467/ (Markdown: https://insights.sbomify.com/CVE-2026-116467/index.md)
```

## Sources

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

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