CVE-2026-43627

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
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 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.

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 computed
Severity78% × 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, 2026
No patch confirmed yet.
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-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)
PackageVulnerable rangeFixed inDependents
llama.cpp10108+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.

  1. 2026-08-20 07:05 UTCGHSA enrichment
  2. 2026-08-19 19:58 UTCEG score recompute
  3. 2026-08-19 19:58 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 08:50 UTCGHSA enrichment
  6. 2026-08-18 21:41 UTCEG score recompute
  7. 2026-08-18 21:41 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 10:10 UTCGHSA enrichment
  10. 2026-08-17 23:03 UTCEG score recompute
  11. 2026-08-17 23:03 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 11:55 UTCGHSA enrichment
  14. 2026-08-17 00:48 UTCEG score recompute
  15. 2026-08-17 00:48 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 13:40 UTCGHSA enrichment
  18. 2026-08-16 02:33 UTCEG score recompute
  19. 2026-08-16 02:33 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 15:26 UTCGHSA enrichment
  22. 2026-08-15 04:18 UTCEG score recompute
  23. 2026-08-15 04:18 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 17:10 UTCEG score recompute
Show 39 more
  1. 2026-08-14 17:10 UTCGHSA enrichment
  2. 2026-08-14 14:04 UTCGHSA enrichment
  3. 2026-08-14 02:56 UTCEG score recompute
  4. 2026-08-14 02:56 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 15:49 UTCGHSA enrichment
  7. 2026-08-13 04:42 UTCGHSA enrichment
  8. 2026-08-12 17:34 UTCEG score recompute
  9. 2026-08-12 17:34 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 06:27 UTCGHSA enrichment
  12. 2026-08-11 19:20 UTCEG score recompute
  13. 2026-08-11 19:20 UTCGHSA enrichment
  14. 2026-08-11 13:43 UTCEPSS rescore
  15. 2026-08-11 08:12 UTCEG score recompute
  16. 2026-08-11 08:12 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 21:05 UTCGHSA enrichment
  19. 2026-08-10 09:57 UTCGHSA enrichment
  20. 2026-08-09 22:50 UTCEG score recompute
  21. 2026-08-09 22:50 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 11:43 UTCGHSA enrichment
  24. 2026-08-09 00:36 UTCEG score recompute
  25. 2026-08-09 00:36 UTCGHSA enrichment
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 13:28 UTCGHSA enrichment
  28. 2026-08-08 02:20 UTCEG score recompute
  29. 2026-08-08 02:20 UTCGHSA enrichment
  30. 2026-08-08 02:12 UTCEG score recompute
  31. 2026-08-08 02:12 UTCGHSA enrichment
  32. 2026-08-07 19:29 UTCEG score recompute
  33. 2026-08-07 19:29 UTCGHSA enrichment
  34. 2026-08-07 19:12 UTCEG score recompute
  35. 2026-08-07 19:12 UTCGHSA enrichment
  36. 2026-08-07 09:25 UTCEG score recompute
  37. 2026-08-07 09:25 UTCGHSA enrichment
  38. 2026-08-06 22:18 UTCEG score recompute
  39. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-43627?
CVE-2026-43627 is a high vulnerability published on August 6, 2026. llama.cpp builds b1283 through b9058 contain an integer overflow vulnerability in the llamabatchinit() 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,…
When was CVE-2026-43627 disclosed?
CVE-2026-43627 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43627 actively exploited?
CVE-2026-43627 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43627?
CVE-2026-43627 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-43627?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43627, 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-43627

Explore →

Is Your Infrastructure Affected by CVE-2026-43627?

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