Skip to content
AI/ML

CVE-2026-43629

9.2
Critical
EPSS 0.62%Aug 7, 2026

Heap overflow in llama.cpp KV cache restore allows code execution via crafted state files

common questions

Is CVE-2026-43629 being exploited?

Not confirmed. CVE-2026-43629 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.62% probability of exploitation in the next 30 days.

How severe is CVE-2026-43629?

CVE-2026-43629 is rated Critical with a CVSS score of 9.2. 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-43629?

Not known from our data. No patch reference has been recorded for CVE-2026-43629, 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-43629 affect?

CVE-2026-43629 affects llama.cpp builds b4882-b9058, Applications embedding vulnerable llama.cpp builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43629?

Restrict write access to slot_save_path; update llama.cpp to a patched commit when available; validate state files.

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

executive summary
technical analysis
affected
llama.cpp builds b4882-b9058Applications embedding vulnerable llama.cpp builds
impact

Heap buffer overflow from crafted KV state files (requires write access to slot_save_path) enabling heap corruption, model tampering, or arbitrary code execution.

action required

Immediate action required

affected versions
ggml-org llama.cpp
  • affected>= b4882 and <= b9058
  • affected>= 0.16.1 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.

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