CVE-2026-18581

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-08-03. A secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.3Exploit: Elevated riskExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A vulnerability was determined in ggml-org llama.cpp e15efe0. Affected by this issue is some unknown functionality of the file common/jinja/parser.cpp of the component Jinja Minja Template Parser. Executing a manipulation with the input {{9|9|{ can lead to reachable assertion. The attack requires local access. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
31
EG Risk 31/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 3, 2026

Last Modified

August 12, 2026

References (8)

Vendor Advisories for CVE-2026-18581(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
llama.cpp10108+dfsg-1 ... 9951+dfsg-3 (59 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-04 12:28 UTCEG score recompute
  3. 2026-10-04 12:28 UTCGHSA enrichment
  4. 2026-10-01 19:49 UTCEPSS rescore
  5. 2026-10-01 10:15 UTCEG score recompute
  6. 2026-10-01 10:15 UTCGHSA enrichment
  7. 2026-09-30 15:02 UTCEPSS rescore
  8. 2026-09-29 15:20 UTCEPSS rescore
  9. 2026-09-28 13:51 UTCEPSS rescore
  10. 2026-09-28 08:32 UTCEG score recompute
  11. 2026-09-28 08:32 UTCGHSA enrichment
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-25 07:32 UTCEG score recompute
  14. 2026-09-25 07:32 UTCGHSA enrichment
  15. 2026-09-22 06:43 UTCEG score recompute
  16. 2026-09-22 06:43 UTCGHSA enrichment
  17. 2026-09-18 17:59 UTCEG score recompute
  18. 2026-09-18 17:59 UTCGHSA enrichment
  19. 2026-09-16 14:07 UTCEPSS rescore
  20. 2026-09-16 05:14 UTCEPSS rescore
  21. 2026-09-15 17:09 UTCEG score recompute
  22. 2026-09-15 17:09 UTCGHSA enrichment
  23. 2026-09-12 15:00 UTCEPSS rescore
  24. 2026-09-12 12:18 UTCEG score recompute
  25. 2026-09-12 12:18 UTCGHSA enrichment
Show 66 more
  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:36 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-09 10:49 UTCEG score recompute
  5. 2026-09-09 10:49 UTCGHSA enrichment
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 09:49 UTCEG score recompute
  10. 2026-09-06 09:49 UTCGHSA enrichment
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-03 08:59 UTCEG score recompute
  13. 2026-09-03 08:59 UTCGHSA enrichment
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-31 02:12 UTCEG score recompute
  17. 2026-08-31 02:12 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-28 01:22 UTCEG score recompute
  22. 2026-08-28 01:22 UTCGHSA enrichment
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 00:28 UTCEG score recompute
  26. 2026-08-25 00:28 UTCGHSA enrichment
  27. 2026-08-23 00:19 UTCEPSS rescore
  28. 2026-08-21 23:38 UTCEG score recompute
  29. 2026-08-21 23:38 UTCGHSA enrichment
  30. 2026-08-20 22:55 UTCEPSS rescore
  31. 2026-08-19 17:03 UTCEPSS rescore
  32. 2026-08-18 22:48 UTCEG score recompute
  33. 2026-08-18 22:48 UTCGHSA enrichment
  34. 2026-08-18 13:48 UTCEPSS rescore
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 02:14 UTCEPSS rescore
  38. 2026-08-15 21:59 UTCEG score recompute
  39. 2026-08-15 21:59 UTCGHSA enrichment
  40. 2026-08-15 01:30 UTCEPSS rescore
  41. 2026-08-13 22:00 UTCEPSS rescore
  42. 2026-08-12 21:09 UTCEG score recompute
  43. 2026-08-12 21:09 UTCGHSA enrichment
  44. 2026-08-12 13:50 UTCEPSS rescore
  45. 2026-08-11 13:42 UTCEPSS rescore
  46. 2026-08-11 00:00 UTCEPSS rescore
  47. 2026-08-09 21:59 UTCEG score recompute
  48. 2026-08-09 21:59 UTCGHSA enrichment
  49. 2026-08-09 13:46 UTCEPSS rescore
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-06 21:09 UTCEG score recompute
  52. 2026-08-06 21:09 UTCGHSA enrichment
  53. 2026-08-06 13:46 UTCEPSS rescore
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:38 UTCEPSS rescore
  57. 2026-08-03 20:20 UTCEG score recompute
  58. 2026-08-03 20:20 UTCGHSA enrichment
  59. 2026-08-03 20:19 UTCNVD updateCVSS v4 → 1.9
  60. 2026-08-03 20:14 UTCEG score recompute
  61. 2026-08-03 20:14 UTCGHSA enrichment
  62. 2026-08-03 20:13 UTCMITRE cvelistV5CVSS v4 → 4.8
  63. 2026-08-03 01:21 UTCEG score recompute
  64. 2026-08-03 01:21 UTCNVD updateCVSS v4 → 1.9
  65. 2026-08-03 01:04 UTCEG score recompute
  66. 2026-08-03 01:03 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-18581?
CVE-2026-18581 is a low vulnerability published on August 3, 2026. A vulnerability was determined in ggml-org llama.cpp e15efe0. Affected by this issue is some unknown functionality of the file common/jinja/parser.cpp of the component Jinja Minja Template Parser. Executing a manipulation with the input {{9|9|{ can lead to reachable assertion. The attack requires…
When was CVE-2026-18581 disclosed?
CVE-2026-18581 was first published on August 3, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18581 actively exploited?
CVE-2026-18581 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18581?
CVE-2026-18581 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18581?
No fix for CVE-2026-18581 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-18581 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18581

Explore →

Is Your Infrastructure Affected by CVE-2026-18581?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs