llama.cpp builds b1283 through b9058 contain an integer overflow vulnerability in the llama_batch_init() function where unchecked multiplications in malloc() calls can wrap past INT32_MAX when computing allocation sizes. Attackers can pass specially crafted parameters to trigger integer overflow, causing heap corruption and potentially achieving arbitrary code execution through subsequent batch operations that write past allocated buffer boundaries.
CVE-2026-43627
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. 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
- 4%
- 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-43627(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 31× in last 7d / 64× 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 07:05 UTCGHSA enrichment
- 2026-08-19 19:58 UTCEG score recompute
- 2026-08-19 19:58 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 08:50 UTCGHSA enrichment
- 2026-08-18 21:41 UTCEG score recompute
- 2026-08-18 21:41 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 10:10 UTCGHSA enrichment
- 2026-08-17 23:03 UTCEG score recompute
- 2026-08-17 23:03 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 11:55 UTCGHSA enrichment
- 2026-08-17 00:48 UTCEG score recompute
- 2026-08-17 00:48 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:40 UTCGHSA enrichment
- 2026-08-16 02:33 UTCEG score recompute
- 2026-08-16 02:33 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 15:26 UTCGHSA enrichment
- 2026-08-15 04:18 UTCEG score recompute
- 2026-08-15 04:18 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:10 UTCEG score recompute
Show 39 moreShow fewer
- 2026-08-14 17:10 UTCGHSA enrichment
- 2026-08-14 14:04 UTCGHSA enrichment
- 2026-08-14 02:56 UTCEG score recompute
- 2026-08-14 02:56 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 15:49 UTCGHSA enrichment
- 2026-08-13 04:42 UTCGHSA enrichment
- 2026-08-12 17:34 UTCEG score recompute
- 2026-08-12 17:34 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 06:27 UTCGHSA enrichment
- 2026-08-11 19:20 UTCEG score recompute
- 2026-08-11 19:20 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 08:12 UTCEG score recompute
- 2026-08-11 08:12 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 21:05 UTCGHSA enrichment
- 2026-08-10 09:57 UTCGHSA enrichment
- 2026-08-09 22:50 UTCEG score recompute
- 2026-08-09 22:50 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 11:43 UTCGHSA enrichment
- 2026-08-09 00:36 UTCEG score recompute
- 2026-08-09 00:36 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 13:28 UTCGHSA enrichment
- 2026-08-08 02:20 UTCEG score recompute
- 2026-08-08 02:20 UTCGHSA enrichment
- 2026-08-08 02:12 UTCEG score recompute
- 2026-08-08 02:12 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:25 UTCEG score recompute
- 2026-08-07 09:25 UTCGHSA enrichment
- 2026-08-06 22:18 UTCEG score recompute
- 2026-08-06 22:15 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-43627?
When was CVE-2026-43627 disclosed?
Is CVE-2026-43627 actively exploited?
What is the CVSS score of CVE-2026-43627?
How do I remediate CVE-2026-43627?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43627
Is Your Infrastructure Affected by CVE-2026-43627?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.