CVE-2026-43622
Double-free in llama.cpp Android JNI causes heap corruption, DoS or potential RCE.
Is CVE-2026-43622 being exploited?
Not confirmed. CVE-2026-43622 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.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-43622?
CVE-2026-43622 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-43622?
Yes. A fix has been recorded for CVE-2026-43622. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43622 affect?
CVE-2026-43622 affects llama.cpp (commits b1886–b7445), LLaMA-Android JNI wrapper, Android apps embedding llama.cpp. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43622?
Update to patched release or rebuild JNI to use matching alloc/free; block untrusted inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
malloc/delete mismatch leads to heap metadata corruption — can crash processes (DoS) or enable arbitrary code execution depending on allocator state.
Immediate action required
- affected>= b1886 and <= b7445
- affected>= 0.9.0 and <= 0.17.1
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.