CVE-2026-33298

Ggml Llama.cpp remote code execution

7.8 HIGHPublic exploitEPSS 0.37%

Published24 Mar 2026

Description

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.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Ggml Llama.cpp< b7824

Remediation

Fixed in

Ggml Llama.cpp≥ b7824

Patch & vendor advisories

https://github.com/ggml-org/llama.cpp/security/advisories/GHSA-96jg-mvhq-q7q7

References

https://github.com/ggml-org/llama.cpp/releases/tag/b7824Release Notes
https://github.com/ggml-org/llama.cpp/security/advisories/GHSA-96jg-mvhq-q7q7ExploitVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-33298 being actively exploited?

CVE-2026-33298 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.37%.

How severe is CVE-2026-33298?

CVE-2026-33298 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.37% probability of exploitation.

Which products are affected by CVE-2026-33298?

Affected products include Ggml Llama.cpp.

How do I fix CVE-2026-33298?

Upgrade affected software to a fixed version, for example Ggml Llama.cpp b7824 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-33298 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.