Code execution via unchecked GGUF tensor dimensions
Published Feb 26, 2024 · Updated Nov 4, 2025
Heap-based buffer overflow in llama.cpp commit 18c2e17 allows context-dependent attackers to execute code via a crafted GGUF file. In gguf_init_from_file, a file-supplied info->n_dims value controls writes beyond the four-element info->ne array without a bounds check. Exploitation requires the loading process to open the malicious model file, after which heap corruption can execute code in that process.
Summary
What happened
Heap-based buffer overflow in llama.cpp commit 18c2e17 allows context-dependent attackers to execute code via a crafted GGUF file. In gguf_init_from_file, a file-supplied info->n_dims value controls writes beyond the four-element info->ne array without a bounds check. Exploitation requires the loading process to open the malicious model file, after which heap corruption can execute code in that process.
The record
- CVE
- CVE-2024-21802
- Published
- Feb 26, 2024
- Updated
- Nov 4, 2025
- Vendor
- Georgi Gerganov
- Product
- llama.cpp
- Classifications
- CWE-122, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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=18c2e17
- Affected versionversion=Commit 18c2e17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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