ggml-org llama.cpp gguf_init_from_file_impl heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in ggml-org llama.cpp. This vulnerability affects the function gguf_init_from_file_impl. Executing a manipulation can lead to heap-based overflow.
This vulnerability is handled as CVE-2026-27940. It is possible to launch the attack on the local host. There is not any exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability has been found in ggml-org llama.cpp (affected version not known) and classified as critical. This vulnerability affects the function gguf_init_from_file_impl. 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. CVE summarizes:
llama.cpp is an inference of several LLM models in C/C++. Prior to b8146, the gguf_init_from_file_impl() in gguf.cpp is vulnerable to an Integer overflow, leading to an undersized heap allocation. Using the subsequent fread() writes 528+ bytes of attacker-controlled data past the buffer boundary. This is a bypass of a similar bug in the same file - CVE-2025-53630, but the fix overlooked some areas. This vulnerability is fixed in b8146.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-27940 since 02/25/2026. The exploitation appears to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 302198 (Linux Distros Unpatched Vulnerability : CVE-2026-27940), which helps to determine the existence of the flaw in a target environment.
Applying the patch b8146 is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at Tenable (302198). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
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 |
Nessus ID: 302198
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-27940
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: b8146
Timeline
02/25/2026 CVE reserved03/12/2026 Advisory disclosed
03/12/2026 VulDB entry created
03/16/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-27940 (🔒)
GCVE (CVE): GCVE-0-2026-27940
GCVE (VulDB): GCVE-100-350716
Entry
Created: 03/12/2026 18:20Updated: 03/16/2026 08:21
Changes: 03/12/2026 18:20 (63), 03/16/2026 08:21 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.