CVE-2026-43627: llama.cpp builds b1283 through b9058 contain an integer overflow vulnerability in the llama_batch_init() function…
CVE-2026-43627 · Severity: high · CVSS 7.8 · Published 2026-08-06
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.
No. Junglewise Threat Intelligence has no report of CVE-2026-43627 being exploited in the wild.
How severe is CVE-2026-43627?
High severity, with a CVSS score of 7.8, published 6 August 2026.
Which products and versions are affected?
GGML Llama.Cpp. The advisory does not name versions.
Is there a fix for CVE-2026-43627?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-43627?
Check whether you run GGML Llama.Cpp. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.