CVE-2026-70638: llama.cpp builds b1886 through b7445 contain an integer overflow vulnerability in the LLaMA-Android JNI wrapper where…

CVE-2026-70638 · Severity: high · CVSS 7.8 · Published 2026-08-06

llama.cpp builds b1886 through b7445 contain an integer overflow vulnerability in the LLaMA-Android JNI wrapper where the new_1batch() function multiplies sizeof(llama_seq_id) by an attacker-controlled n_seq_max parameter without overflow validation, causing heap buffer allocation to wrap and allocate insufficient memory. Attackers can exploit this by providing a crafted n_seq_max value through a malicious model file or JNI call to trigger heap corruption and achieve denial of service or arbitrary code execution on Android applications using the LLaMA-Android binding.

Technologies: GGML Llama.Cpp. Vendors: GGML.

Quick answers

Is CVE-2026-70638 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-70638 being exploited in the wild.
How severe is CVE-2026-70638?
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-70638?
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-70638?
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.

Affected products

  • GGML Llama.Cpp

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.