CVE-2026-43622

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-06. 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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

llama.cpp builds b1886 through b7445 contain a double free vulnerability in the LLaMA-Android JNI wrapper where new_1batch() allocates memory using malloc() while free_1batch() deallocates it using the C++ delete operator, causing heap metadata corruption. Attackers can trigger this memory management mismatch to cause denial of service through process crashes or potentially achieve arbitrary code execution depending on allocator state.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 6, 2026

Last Modified

September 4, 2026

Advisory Details (3)

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

b7446

Patch available: ggml-org/llama.cpp b7446

https://github.com/ggml-org/llama.cpp/releases/tag/b7446
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
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

Vendor Advisories for CVE-2026-43622(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 rangeFix by version rangeDependents
llama.cpp5151+dfsg-1~exp2 ... 6641+dfsg-3 (19 versions)
  • every version up to 7593+dfsg-1: fixed in 7593+dfsg-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 89× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43622?
CVE-2026-43622 is a high vulnerability published on August 6, 2026. llama.cpp builds b1886 through b7445 contain a double free vulnerability in the LLaMA-Android JNI wrapper where new1batch() allocates memory using malloc() while free1batch() deallocates it using the C++ delete operator, causing heap metadata corruption. Attackers can trigger this memory management…
When was CVE-2026-43622 disclosed?
CVE-2026-43622 was first published on August 6, 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-43622 actively exploited?
CVE-2026-43622 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43622?
CVE-2026-43622 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-43622?
A fix for CVE-2026-43622 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43622 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-43622?

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