Code execution via unchecked KV cache write
Published Aug 6, 2026 · Updated Aug 6, 2026
Heap buffer overflow in llama.cpp 0.16.1 through 0.17.1 allows attackers to corrupt process memory via crafted KV cache state files. The state_read_data() path multiplies attacker-controlled cell_count values by tensor row sizes and passes unchecked offsets and lengths to read_tensor(). Exploitation requires write access to slot_save_path and a later restore operation; successful corruption can execute code in the server process.
Summary
What happened
Heap buffer overflow in llama.cpp 0.16.1 through 0.17.1 allows attackers to corrupt process memory via crafted KV cache state files. The state_read_data() path multiplies attacker-controlled cell_count values by tensor row sizes and passes unchecked offsets and lengths to read_tensor(). Exploitation requires write access to slot_save_path and a later restore operation; successful corruption can execute code in the server process.
The record
- CVE
- CVE-2026-43629
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Georgi Gerganov
- Product
- llama.cpp
- Classifications
- CWE-190, CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.16.1 <=0.17.1
- Affected versionversion=b4882 <=b9058
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo