ggml-org llama.cpp up to 0.7.0 Mirostat Sampler src/llama-sampler.cpp assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.66 |
Summary
A vulnerability was found in ggml-org llama.cpp up to 0.7.0. It has been classified as problematic. Affected by this issue is some unknown functionality of the file src/llama-sampler.cpp of the component Mirostat Sampler. This manipulation causes assertion. This vulnerability is handled as CVE-2026-116467. The attack can be initiated remotely. There is not any exploit available. The project was informed of the problem early through a pull request but has not reacted yet.
Details
A vulnerability has been found in ggml-org llama.cpp up to 0.7.0 and classified as problematic. Affected by this vulnerability is an unknown code block of the file src/llama-sampler.cpp of the component Mirostat Sampler. The manipulation with an unknown input leads to a assertion vulnerability. The CWE definition for the vulnerability is CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. As an impact it is known to affect availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-116467. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The project was informed of the problem early through a pull request but has not reacted yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AssertionCWE: CWE-617
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/26/2026 Advisory disclosed10/26/2026 VulDB entry created
10/26/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 29992
Status: Confirmed
CVE: CVE-2026-116467 (🔒)
GCVE (CVE): GCVE-0-2026-116467
GCVE (VulDB): GCVE-100-426361
Entry
Created: 10/26/2026 11:22Changes: 10/26/2026 11:22 (55)
Complete: 🔍
Submitter: Jasmine-tim
Cache ID: 216::103
Submit
Accepted
- Submit #1013917: ggml-org llama.cpp 2ed93db47 and earlier (fixed in PR #29992) CWE-617 (Reachable Assertion) (by Jasmine-tim)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.