CVE-2026-34159

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.1%, top 36% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

llama.cpp is an inference of several LLM models in C/C++. Prior to version b8492, the RPC backend's deserialize_tensor() skips all bounds validation when a tensor's buffer field is 0. An unauthenticated attacker can read and write arbitrary process memory via crafted GRAPH_COMPUTE messages. Combined with pointer leaks from ALLOC_BUFFER/BUFFER_GET_BASE, this gives full ASLR bypass and remote code execution. No authentication required, just TCP access to the RPC server port. This issue has been patched in version b8492.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
64%
KEV
Not listed

Published

April 1, 2026

Last Modified

April 30, 2026

Advisory Details (3)

Auto-updated Sep 9, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available🟡 PoC Available

Unauthenticated RCE via GRAPH_COMPUTE buffer=0 bypass in llama.cpp RPC backend · Advisory · ggml-org/llama.cpp · GitHub

https://github.com/ggml-org/llama.cpp/security/advisories/GHSA-j8rj-fmpv-wcxw
github_pr

RPC GRAPH_COMPUTE Arbitrary RCE patch

Fix merged in ggml-org/llama.cpp PR #20908 on 2026-03-23 — awaiting tagged release

https://github.com/ggml-org/llama.cpp/pull/20908
github_commit

commit 39bf0d3c6a95 (ggml-org/llama.cpp)

Fix landed in ggml-org/llama.cpp commit 39bf0d3c6a95 — awaiting tagged release

https://github.com/ggml-org/llama.cpp/commit/39bf0d3c6a95803e0f41aaba069ffbee26721042

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
llama.cpp5151+dfsg-1~exp2 ... 8461+dfsg-1 (26 versions)8611+dfsg-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-02 11:44 UTCOSV refresh
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 09:29 UTCEG score recompute
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 05:55 UTCEG score recompute
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 20:12 UTCEG score recompute
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-11 20:33 UTCEG score recompute
  13. 2026-08-11 03:33 UTCEG score recompute
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-09 17:12 UTCEG score recompute
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-09 05:28 UTCEG score recompute
  18. 2026-08-08 16:37 UTCEPSS rescore
  19. 2026-08-07 19:46 UTCEG score recompute
  20. 2026-08-06 18:04 UTCEG score recompute
  21. 2026-08-06 13:46 UTCEPSS rescore
  22. 2026-08-06 00:29 UTCEG score recompute
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-04 15:10 UTCEPSS rescore
  25. 2026-08-04 10:38 UTCEPSS rescore
  26. 2026-08-03 22:49 UTCEG score recompute
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 14:46 UTCEG score recompute
  29. 2026-08-02 02:27 UTCEPSS rescore
  30. 2026-08-01 04:16 UTCEPSS rescore
  31. 2026-07-30 16:28 UTCEPSS rescore
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-27 14:13 UTCEPSS rescore
  34. 2026-07-25 14:18 UTCEPSS rescore
  35. 2026-07-25 14:18 UTCEPSS rescore
  36. 2026-07-24 14:17 UTCEPSS rescore
  37. 2026-07-24 14:17 UTCEPSS rescore
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 14:18 UTCEPSS rescore
  40. 2026-07-23 03:09 UTCEG score recompute
  41. 2026-07-22 14:08 UTCEPSS rescore
  42. 2026-07-21 15:24 UTCEPSS rescore
  43. 2026-07-20 17:08 UTCEPSS rescore
  44. 2026-07-19 14:31 UTCEPSS rescore
  45. 2026-07-19 02:29 UTCEPSS rescore
  46. 2026-07-18 10:04 UTCEPSS rescore
  47. 2026-07-17 20:29 UTCOSV refresh
  48. 2026-07-16 17:03 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 02:00 UTCEPSS rescore
  52. 2026-07-13 22:30 UTCEPSS rescore
  53. 2026-07-13 06:13 UTCEPSS rescore
  54. 2026-07-13 06:13 UTCEPSS rescore
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-09 19:10 UTCEPSS rescore
  58. 2026-07-08 15:15 UTCEPSS rescore
  59. 2026-07-07 13:46 UTCEPSS rescore
  60. 2026-07-06 16:27 UTCEPSS rescore
  61. 2026-07-06 16:27 UTCEPSS rescore
  62. 2026-07-06 02:23 UTCEPSS rescore
  63. 2026-07-06 02:23 UTCEPSS rescore
  64. 2026-07-05 02:30 UTCEPSS rescore
  65. 2026-07-04 06:31 UTCEPSS rescore
  66. 2026-07-01 15:06 UTCEPSS rescore
  67. 2026-06-30 23:22 UTCEPSS rescore
  68. 2026-06-29 14:06 UTCEPSS rescore
  69. 2026-06-29 14:06 UTCEPSS rescore
  70. 2026-06-28 14:07 UTCEPSS rescore
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-28 04:56 UTCEPSS rescore
  73. 2026-06-28 04:56 UTCEPSS rescore
  74. 2026-06-27 03:08 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCcasp3r0x0/CVE-2026-34159
    First seen Apr 23, 2026

    0 Click RCE exploit for CVE-2026-34159 Lama.cpp RPC server

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-34159?
CVE-2026-34159 is a critical vulnerability published on April 1, 2026. llama.cpp is an inference of several LLM models in C/C++. Prior to version b8492, the RPC backend's deserializetensor() skips all bounds validation when a tensor's buffer field is 0. An unauthenticated attacker can read and write arbitrary process memory via crafted GRAPHCOMPUTE messages. Combined…
When was CVE-2026-34159 disclosed?
CVE-2026-34159 was first published in the National Vulnerability Database on April 1, 2026, with the most recent update on April 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34159 actively exploited?
CVE-2026-34159 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 35.5% of all scored CVEs.
What is the CVSS score of CVE-2026-34159?
CVE-2026-34159 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-34159?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34159, 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-34159

Explore →

Is Your Infrastructure Affected by CVE-2026-34159?

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

Start Free Scan →Browse All CVEs