Critical Memory Leak in Ollama
Key point
A vulnerability in Ollama's GGUF processing allowed process memory, prompts, and environment variables to be leaked without authentication.
Details
Cyera Research disclosed CVE-2026-7482 (CVSS 9.1) in Ollama. An attacker can exploit the model creation path without authentication to read the entire Ollama process memory, and the exposed scope includes user prompts, system prompts, and environment variables.
The vulnerability occurs during the process of converting an uploaded GGUF file into a model.
/api/createreads the GGUF and turns it into aLayer, then performs quantization if needed.WriteTocallsConvertToF32based on the element count computed byElements(), instead of the tensor's actual byte size.- If an attacker manipulates the GGUF's shape values to be abnormally large, a heap out-of-bounds read occurs, exceeding the actual buffer.
- The read memory can be converted and saved again, getting mixed into the model file, allowing sensitive information to be leaked continuously.
The root cause is Go's use of unsafe combined with a design that fails to verify whether the shape values match the actual data size. The article claims that roughly 300,000 servers worldwide may be affected.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.