Skip to content
AI/ML

CVE-2026-70638

8.5
High
EPSS 0.21%Aug 7, 2026

Integer overflow in LLaMA-Android JNI causes heap corruption, DoS or RCE.

common questions

Is CVE-2026-70638 being exploited?

Not confirmed. CVE-2026-70638 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.

How severe is CVE-2026-70638?

CVE-2026-70638 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-70638?

Not known from our data. No patch reference has been recorded for CVE-2026-70638, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-70638 affect?

CVE-2026-70638 affects llama.cpp builds b1886–b7445, LLaMA-Android JNI wrapper, Android apps using LLaMA-Android binding, Apps loading untrusted model files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-70638?

Do not load untrusted models; restrict app privileges; apply upstream patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
llama.cpp builds b1886–b7445LLaMA-Android JNI wrapperAndroid apps using LLaMA-Android bindingApps loading untrusted model files
impact

Crafted n_seq_max in a model file or JNI call triggers integer overflow and heap buffer wrap, enabling denial of service or arbitrary code execution on Android apps using LLaMA-Android.

action required

Immediate action required

affected versions
ggml-org llama.cpp
  • affected>= b1886 and <= b7445
  • affected>= 0.9.0 and <= 0.17.1
vendor says fixed in5c0d18881e0e9794c96b2602736b758bac9d9388

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free