llama.cpp before b8585 contains a use-after-free vulnerability in the RPC server's GRAPH_RECOMPUTE handler that allows unauthenticated remote attackers to achieve arbitrary read and write access by storing a computation graph, freeing referenced buffers, and reclaiming freed memory with attacker-controlled content. Attackers can send RPC requests to trigger re-execution of stored graphs with dangling pointers, enabling full remote code execution without requiring authentication or user interaction.
CVE-2026-39909
HIGHPre-NVD 8.18.1
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:vulncheck
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.1Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(low)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (4)
Auto-updated Aug 21, 2026Patch available. Sources: github_release, github_pr, github_commit.
generic
llama.cpp Use-After-Free in RPC GRAPH_RECOMPUTE Handler | Advisories | VulnCheck
https://www.vulncheck.com/advisories/llama-cpp-use-after-free-in-rpc-graph-recompute-handlergithub_commit
commit 389c7d4955ba (ggml-org/llama.cpp)
Fix landed in ggml-org/llama.cpp commit 389c7d4955ba — awaiting tagged release
https://github.com/ggml-org/llama.cpp/commit/389c7d4955ba55c7418afaebf7c23d9ed64ef707github_pr
webui: Fix branching logic on edit message
Fix merged in ggml-org/llama.cpp PR #21175 on 2026-03-30 — awaiting tagged release
https://github.com/ggml-org/llama.cpp/pull/21175github_release Patch Available
b8585
Patch available: ggml-org/llama.cpp b8585
https://github.com/ggml-org/llama.cpp/releases/tag/b8585Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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.
- 2026-08-21 16:51 UTCEG score recompute
- 2026-08-21 16:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-39909?
CVE-2026-39909 is a high vulnerability published on August 21, 2026. llama.cpp before b8585 contains a use-after-free vulnerability in the RPC server's GRAPH_RECOMPUTE handler that allows unauthenticated remote attackers to achieve arbitrary read and write access by storing a computation graph, freeing referenced buffers, and reclaiming freed memory with…
When was CVE-2026-39909 disclosed?
CVE-2026-39909 was first published in the National Vulnerability Database on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-39909?
CVE-2026-39909 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-39909?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39909, 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
Explore the affected products and dependency analysis for CVE-2026-39909
Is Your Infrastructure Affected by CVE-2026-39909?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.