CVE-2026-70638

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
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.8Exploit: 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 an integer overflow vulnerability in the LLaMA-Android JNI wrapper where the new_1batch() function multiplies sizeof(llama_seq_id) by an attacker-controlled n_seq_max parameter without overflow validation, causing heap buffer allocation to wrap and allocate insufficient memory. Attackers can exploit this by providing a crafted n_seq_max value through a malicious model file or JNI call to trigger heap corruption and achieve denial of service or arbitrary code execution on Android applications using the LLaMA-Android binding.

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

Published

August 6, 2026

Last Modified

August 31, 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-70638(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 22× in last 7d / 96× 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 166 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-70638?
CVE-2026-70638 is a high vulnerability published on August 6, 2026. llama.cpp builds b1886 through b7445 contain an integer overflow vulnerability in the LLaMA-Android JNI wrapper where the new1batch() function multiplies sizeof(llamaseqid) by an attacker-controlled nseqmax parameter without overflow validation, causing heap buffer allocation to wrap and allocate…
When was CVE-2026-70638 disclosed?
CVE-2026-70638 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70638 actively exploited?
CVE-2026-70638 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 88.6% of all scored CVEs.
What is the CVSS score of CVE-2026-70638?
CVE-2026-70638 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-70638?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70638, 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-70638

Explore →

Is Your Infrastructure Affected by CVE-2026-70638?

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

Start Free Scan →Browse All CVEs