ggml-org llama.cpp up to 55abc39/up to 55d4206c8 GGUF File Parser ggml_nbytes heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 10.00 |
Summary
A vulnerability identified as critical has been detected in ggml-org llama.cpp. This affects the function ggml_nbytes of the component GGUF File Parser. This manipulation causes heap-based overflow.
This vulnerability is registered as CVE-2026-33298. The attack needs to be launched locally. No exploit is available.
You should upgrade the affected component.
Details
A vulnerability classified as critical was found in ggml-org llama.cpp. Affected by this vulnerability is the function ggml_nbytes of the component GGUF File Parser. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
llama.cpp is an inference of several LLM models in C/C++. Prior to b7824, an integer overflow vulnerability in the `ggml_nbytes` function allows an attacker to bypass memory validation by crafting a GGUF file with specific tensor dimensions. This causes `ggml_nbytes` to return a significantly smaller size than required (e.g., 4MB instead of Exabytes), leading to a heap-based buffer overflow when the application subsequently processes the tensor. This vulnerability allows potential Remote Code Execution (RCE) via memory corruption. b7824 contains a fix.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-33298 since 03/18/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version b7824 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: llama.cpp b7824
Timeline
03/18/2026 CVE reserved03/24/2026 Advisory disclosed
03/24/2026 VulDB entry created
03/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-96jg-mvhq-q7q7
Status: Confirmed
CVE: CVE-2026-33298 (🔒)
GCVE (CVE): GCVE-0-2026-33298
GCVE (VulDB): GCVE-100-352585
Entry
Created: 03/24/2026 02:27Updated: 03/28/2026 09:37
Changes: 03/24/2026 02:27 (67), 03/28/2026 09:37 (1)
Complete: 🔍
Cache ID: 216:9B2:103
No comments yet. Languages: en.
Please log in to comment.