GPU VulnDB

Database/AI/ML frameworks & serving

llama.cpp: integer overflow in GGUF tensor shape validation leads to out-of-bounds memory access

CVSS 6.9CVE-2026-116829AI/ML frameworks & servingcurated

Impact

A crafted GGUF file can carry tensor extents whose product wraps to zero, slipping past the element-count check. ggml_nbytes() and the stride computation then overflow, buffers are sized from the wrapped byte count, and the loader reads and writes outside them. Any pipeline that loads operator- or tenant-supplied GGUF files - a model-serving worker, a conversion job, a shared inference host pulling weights from a registry - can be crashed, and the out-of-bounds access makes memory corruption in the loading process plausible. This is a distinct bug from the earlier tensor-offset out-of-bounds read: different check, different fix, different release.

Who can reach it

Local with user interaction per the CVSS vector: someone or something must load the malicious GGUF file. In practice that is whoever can place a model file where the serving process will read it - a tenant uploading weights, or a compromised model registry.

What to do

Upgrade llama.cpp to build b11301 or later (fix commit 2149c00f) and restart the serving processes. No node or firmware maintenance. Until then, only load GGUF files from sources you control and validate them out of band.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.