CVE-2026-52131

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

llama.cpp b5693 and before has a Reachable Assertion via the gguf_reader::read function.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 4, 2026

Advisory Details (2)

Auto-updated Sep 2, 2026
No patch confirmed yet.
generic

llama.cpp json-schema-to-grammar 무제어 재귀 DoS — Ph4nt0m

https://blog.ph4nt0m.xyz/ko/cves/cve-2026-52130/
generic

GitHub - ggml-org/llama.cpp: LLM inference in C/C++ · GitHub

https://github.com/ggml-org/llama.cpp

Vendor Advisories for CVE-2026-52131(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 rangeFixed inDependents
llama.cpp10108+dfsg-1 ... 9951+dfsg-3 (55 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 71× 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-09-20 00:05 UTCEG score recompute
  2. 2026-09-20 00:05 UTCGHSA enrichment
  3. 2026-09-19 12:42 UTCGHSA enrichment
  4. 2026-09-19 01:19 UTCEG score recompute
  5. 2026-09-19 01:19 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 13:57 UTCGHSA enrichment
  8. 2026-09-18 02:27 UTCEG score recompute
  9. 2026-09-18 02:27 UTCGHSA enrichment
  10. 2026-09-17 15:04 UTCGHSA enrichment
  11. 2026-09-17 03:41 UTCGHSA enrichment
  12. 2026-09-16 16:18 UTCEG score recompute
  13. 2026-09-16 16:18 UTCGHSA enrichment
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-16 04:53 UTCGHSA enrichment
  17. 2026-09-15 17:30 UTCGHSA enrichment
  18. 2026-09-15 06:05 UTCEG score recompute
  19. 2026-09-15 06:05 UTCGHSA enrichment
  20. 2026-09-14 18:40 UTCGHSA enrichment
  21. 2026-09-14 07:08 UTCGHSA enrichment
  22. 2026-09-13 19:46 UTCEG score recompute
  23. 2026-09-13 19:46 UTCGHSA enrichment
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-13 08:23 UTCGHSA enrichment
Show 46 more
  1. 2026-09-12 21:01 UTCEG score recompute
  2. 2026-09-12 21:01 UTCGHSA enrichment
  3. 2026-09-12 09:38 UTCGHSA enrichment
  4. 2026-09-11 22:15 UTCEG score recompute
  5. 2026-09-11 22:15 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 10:49 UTCEG score recompute
  8. 2026-09-11 10:49 UTCGHSA enrichment
  9. 2026-09-10 23:02 UTCGHSA enrichment
  10. 2026-09-10 11:39 UTCEG score recompute
  11. 2026-09-10 11:39 UTCGHSA enrichment
  12. 2026-09-10 09:35 UTCEPSS rescore
  13. 2026-09-09 23:41 UTCGHSA enrichment
  14. 2026-09-09 10:50 UTCGHSA enrichment
  15. 2026-09-08 23:28 UTCEG score recompute
  16. 2026-09-08 23:28 UTCGHSA enrichment
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 04:13 UTCGHSA enrichment
  19. 2026-09-07 16:50 UTCEG score recompute
  20. 2026-09-07 16:50 UTCGHSA enrichment
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-07 05:27 UTCGHSA enrichment
  23. 2026-09-06 17:59 UTCEG score recompute
  24. 2026-09-06 17:59 UTCGHSA enrichment
  25. 2026-09-06 13:47 UTCEPSS rescore
  26. 2026-09-06 06:36 UTCGHSA enrichment
  27. 2026-09-05 19:13 UTCEG score recompute
  28. 2026-09-05 19:13 UTCGHSA enrichment
  29. 2026-09-05 07:51 UTCGHSA enrichment
  30. 2026-09-04 20:28 UTCGHSA enrichment
  31. 2026-09-04 17:09 UTCEG score recompute
  32. 2026-09-04 17:09 UTCGHSA enrichment
  33. 2026-09-04 05:45 UTCEG score recompute
  34. 2026-09-04 05:45 UTCGHSA enrichment
  35. 2026-09-04 05:06 UTCEPSS rescore
  36. 2026-09-03 18:20 UTCGHSA enrichment
  37. 2026-09-03 06:57 UTCEG score recompute
  38. 2026-09-03 06:57 UTCGHSA enrichment
  39. 2026-09-02 19:33 UTCGHSA enrichment
  40. 2026-09-02 18:44 UTCEG score recompute▲ 7.50
  41. 2026-09-02 18:43 UTCGHSA enrichment
  42. 2026-09-02 18:41 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  43. 2026-09-02 14:12 UTCEPSS rescore
  44. 2026-09-01 18:22 UTCNVD update
  45. 2026-09-01 17:22 UTCEG score recompute
  46. 2026-09-01 17:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-52131?
CVE-2026-52131 is a high vulnerability published on September 1, 2026. llama.cpp b5693 and before has a Reachable Assertion via the gguf_reader::read function.
When was CVE-2026-52131 disclosed?
CVE-2026-52131 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52131 actively exploited?
CVE-2026-52131 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.6% of all scored CVEs.
What is the CVSS score of CVE-2026-52131?
CVE-2026-52131 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-52131?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52131, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-52131?

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

Start Free Scan →Browse All CVEs