Quick answers
- Is CVE-2026-116467 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116467 being exploited in the wild.
- How severe is CVE-2026-116467?
- Medium severity, with a CVSS score of 5.3, published 26 October 2026.
- Which products and versions are affected?
- Ggml-Org Llama.Cpp up to 0.7.0.
- Is there a fix for CVE-2026-116467?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-116467 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116467?
- Check whether you run Ggml-Org Llama.Cpp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Mirostat Sampler component in src/llama-sampler.cpp fails to guard against non-finite (NaN or infinity) logits and probabilities, resulting in undefined behavior (float-cast-overflow) or assertion failures. Both Mirostat v1 and v2 variants are reachable remotely via the llama-server interface when mirostat=1 or mirostat=2, allowing an attacker to cause an abort or crash without authentication.
Affected products
- ggml-org llama.cpp up to 0.7.0
Timeline
- 2026-10-26: disclosed
- 2026-10-05: other: Pull request #29992 submitted with fix but not yet merged