ggml-org llama.cpp e15efe0 Jinja Minja Template Parser common/jinja/parser.cpp assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 2.28- |
Summary
A vulnerability has been found in ggml-org llama.cpp e15efe0 and classified as problematic. This affects an unknown part of the file common/jinja/parser.cpp of the component Jinja Minja Template Parser. The manipulation with the input {{9|9|{ leads to assertion.
This vulnerability is traded as CVE-2026-18581. An attack has to be approached locally. Furthermore, there is an exploit available.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability, which was classified as problematic, has been found in ggml-org llama.cpp e15efe0. This issue affects an unknown part of the file common/jinja/parser.cpp of the component Jinja Minja Template Parser. The manipulation with the input value {{9|9|{ leads to a assertion vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-18581. The exploitation is known to be easy. An attack has to be approached locally. Technical details as well as a public exploit are known.
The exploit is available at drive.proton.me. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded 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: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
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: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
08/02/2026 Advisory disclosed08/02/2026 VulDB entry created
08/02/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 25282
Status: Not defined
CVE: CVE-2026-18581 (🔒)
GCVE (CVE): GCVE-0-2026-18581
GCVE (VulDB): GCVE-100-385409
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/02/2026 21:03Changes: 08/02/2026 21:03 (59)
Complete: 🔍
Submitter: m00dy
Cache ID: 216::103
Submit
Accepted
- Submit #799118: ggml-org llama.cpp confirmed commit e15efe0 CWE-617 (Reachable Assertion) (by m00dy)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.