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.
CVE-2026-43622
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-06. the CNA's CVSS baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- 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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 6, 2026
Last Modified
August 14, 2026
Advisory Details (3)
Auto-updated Aug 6, 2026b7446
Patch available: ggml-org/llama.cpp b7446
https://github.com/ggml-org/llama.cpp/releases/tag/b7446commit 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/5c0d18881e0e9794c96b2602736b758bac9d9388GitHub - 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-patchesVendor 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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| llama.cpp | 5151+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 30× in last 7d / 62× 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-20 10:24 UTCGHSA enrichment
- 2026-08-19 23:01 UTCEG score recompute
- 2026-08-19 23:01 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 11:36 UTCGHSA enrichment
- 2026-08-19 00:12 UTCEG score recompute
- 2026-08-19 00:12 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 12:48 UTCGHSA enrichment
- 2026-08-18 00:59 UTCEG score recompute
- 2026-08-18 00:59 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 13:35 UTCGHSA enrichment
- 2026-08-17 02:11 UTCEG score recompute
- 2026-08-17 02:11 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:47 UTCGHSA enrichment
- 2026-08-16 03:23 UTCEG score recompute
- 2026-08-16 03:23 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 15:59 UTCGHSA enrichment
- 2026-08-15 04:35 UTCEG score recompute
- 2026-08-15 04:35 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:10 UTCEG score recompute
Show 37 moreShow fewer
- 2026-08-14 17:10 UTCGHSA enrichment
- 2026-08-14 11:04 UTCGHSA enrichment
- 2026-08-13 23:40 UTCEG score recompute
- 2026-08-13 23:40 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:16 UTCGHSA enrichment
- 2026-08-13 00:52 UTCEG score recompute
- 2026-08-13 00:52 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 13:29 UTCGHSA enrichment
- 2026-08-12 02:05 UTCGHSA enrichment
- 2026-08-11 14:41 UTCEG score recompute
- 2026-08-11 14:41 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 03:17 UTCEG score recompute
- 2026-08-11 03:17 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 15:54 UTCGHSA enrichment
- 2026-08-10 04:28 UTCGHSA enrichment
- 2026-08-09 17:04 UTCEG score recompute
- 2026-08-09 17:04 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 05:41 UTCGHSA enrichment
- 2026-08-08 18:17 UTCEG score recompute
- 2026-08-08 18:17 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 06:53 UTCGHSA enrichment
- 2026-08-07 19:29 UTCEG score recompute
- 2026-08-07 19:29 UTCGHSA enrichment
- 2026-08-07 19:12 UTCEG score recompute
- 2026-08-07 19:12 UTCGHSA enrichment
- 2026-08-07 09:46 UTCGHSA enrichment
- 2026-08-06 22:22 UTCEG score recompute
- 2026-08-06 22:22 UTCGHSA enrichment
- 2026-08-06 16:32 UTCEG score recompute
- 2026-08-06 15:31 UTCEG score recompute
- 2026-08-06 15:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-415
- CVE-2007-4773EG 9.8CRITICAL
- CVE-2016-8619NVD 5.3EG 9.8EPSS p92CRITICAL
- CVE-2016-8618NVD 5.3EG 9.8EPSS p91CRITICAL
- CVE-2015-9165EG 9.8CRITICAL
- CVE-2017-18201EG 9.8CRITICAL
- CVE-2017-18174EG 9.8CRITICAL
- CVE-2017-1000232EG 9.8CRITICAL
- CVE-2017-1000231EG 9.8CRITICAL
- CVE-2017-16820EG 9.8EPSS p90CRITICAL
- CVE-2017-14952EG 9.8EPSS p92CRITICAL
Frequently asked(5)
What is CVE-2026-43622?
When was CVE-2026-43622 disclosed?
Is CVE-2026-43622 actively exploited?
What is the CVSS score of CVE-2026-43622?
How do I remediate CVE-2026-43622?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43622
Is Your Infrastructure Affected by CVE-2026-43622?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.