CVE-2026-70640

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. the CNA's CVSS baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 0

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

llama.cpp builds b1886 through b7445 contain a race condition use-after-free vulnerability in the LLaMA-Android JNI wrapper where bench_1model() and free_1context() lack synchronization, allowing Thread A to operate on freed memory while Thread B concurrently frees the llama_context. Attackers can exploit this by performing heap spray with attacker-controlled data containing a fake vtable to hijack the vtable pointer at offset +0x30, causing llama_batch_allocr::clear() to dereference arbitrary memory and achieve remote code execution.

CVSS v3
7.0
EG Score
7.0(high)
EG Risk
32(Track)
EG Risk 32/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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 14, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_release, github_commit.
generic

GitHub - Vladimir-tokarev-cyera/llama-cpp-security-patches: Security patches for unpatched llama.cpp vulnerabilities (CVE-2026-43626 through CVE-2026-43632) — Cyera Research · GitHub

https://github.com/Vladimir-tokarev-cyera/llama-cpp-security-patches
github_commit

commit 5c0d18881e0e (ggml-org/llama.cpp)

Fix landed in ggml-org/llama.cpp commit 5c0d18881e0e — awaiting tagged release

https://github.com/ggml-org/llama.cpp/commit/5c0d18881e0e9794c96b2602736b758bac9d9388
github_release Patch Available

b7446

Patch available: ggml-org/llama.cpp b7446

https://github.com/ggml-org/llama.cpp/releases/tag/b7446

Vendor Advisories for CVE-2026-70640(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.cpp5151+dfsg-1~exp2 ... 6641+dfsg-3 (19 versions)7593+dfsg-1—

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-70640?
CVE-2026-70640 is a high vulnerability published on August 6, 2026. llama.cpp builds b1886 through b7445 contain a race condition use-after-free vulnerability in the LLaMA-Android JNI wrapper where bench1model() and free1context() lack synchronization, allowing Thread A to operate on freed memory while Thread B concurrently frees the llamacontext. Attackers can…
When was CVE-2026-70640 disclosed?
CVE-2026-70640 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70640 actively exploited?
CVE-2026-70640 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 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-70640?
CVE-2026-70640 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-70640?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70640, 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-70640

Explore →

Is Your Infrastructure Affected by CVE-2026-70640?

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

Start Free Scan →Browse All CVEs