llama.cpp builds b4882 through b9058 contain a heap buffer overflow vulnerability in the KV cache state restore path where the state_read_data() function computes write size without overflow checking, allowing attackers with write access to the slot_save_path directory to corrupt heap memory. Attackers can craft malicious state files where cell_count multiplication overflows or exceeds tensor buffer allocation to write attacker-controlled bytes past buffer boundaries, potentially resulting in heap metadata corruption, model weight corruption, or arbitrary code execution via function pointer overwrite.
CVE-2026-43629
Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-07. the CNA's CVSS baseline 8.1; 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
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/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%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 47%
- KEV
- Not listed
Published
August 6, 2026
Last Modified
August 14, 2026
Advisory Details (1)
Auto-updated Aug 6, 2026GitHub - 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-43629(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 | 10108+dfsg-1 ... 9951+dfsg-3 (50 versions) | — | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 30× in last 7d / 66× 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 16:49 UTCGHSA enrichment
- 2026-08-20 05:46 UTCGHSA enrichment
- 2026-08-19 18:49 UTCEG score recompute
- 2026-08-19 18:49 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 06:47 UTCGHSA enrichment
- 2026-08-18 19:45 UTCEG score recompute
- 2026-08-18 19:45 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 08:47 UTCGHSA enrichment
- 2026-08-17 21:51 UTCEG score recompute
- 2026-08-17 21:51 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:50 UTCGHSA enrichment
- 2026-08-16 23:54 UTCEG score recompute
- 2026-08-16 23:54 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:57 UTCEG score recompute
- 2026-08-16 12:57 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 02:01 UTCGHSA enrichment
- 2026-08-15 15:04 UTCGHSA enrichment
- 2026-08-15 04:07 UTCEG score recompute
- 2026-08-15 04:07 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
Show 41 moreShow fewer
- 2026-08-14 17:10 UTCEG score recompute
- 2026-08-14 17:10 UTCGHSA enrichment
- 2026-08-14 15:35 UTCGHSA enrichment
- 2026-08-14 04:39 UTCEG score recompute
- 2026-08-14 04:39 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 17:42 UTCGHSA enrichment
- 2026-08-13 06:46 UTCGHSA enrichment
- 2026-08-12 19:49 UTCEG score recompute
- 2026-08-12 19:49 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 08:53 UTCGHSA enrichment
- 2026-08-11 21:56 UTCEG score recompute
- 2026-08-11 21:56 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 11:00 UTCGHSA enrichment
- 2026-08-11 00:04 UTCEG score recompute
- 2026-08-11 00:04 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 13:07 UTCGHSA enrichment
- 2026-08-10 02:11 UTCGHSA enrichment
- 2026-08-09 15:14 UTCEG score recompute
- 2026-08-09 15:14 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 04:18 UTCGHSA enrichment
- 2026-08-08 17:22 UTCEG score recompute
- 2026-08-08 17:22 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 06:25 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 18:27 UTCEG score recompute
- 2026-08-07 18:27 UTCGHSA enrichment
- 2026-08-07 17:28 UTCEG score recompute
- 2026-08-07 17:28 UTCGHSA enrichment
- 2026-08-07 09:14 UTCEG score recompute
- 2026-08-07 09:14 UTCGHSA enrichment
- 2026-08-06 22:18 UTCEG score recompute
- 2026-08-06 22:15 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-787
Frequently asked(5)
What is CVE-2026-43629?
When was CVE-2026-43629 disclosed?
Is CVE-2026-43629 actively exploited?
What is the CVSS score of CVE-2026-43629?
How do I remediate CVE-2026-43629?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43629
Is Your Infrastructure Affected by CVE-2026-43629?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.