Ollama heap out-of-bounds read in GGUF tensor parsing leaks server process memory to unauthenticated remote attackers
63Vexday Risk Score
Prioritize patching. It exploitation observed by VulnCheck and has a public proof of concept.
ssvc Actcvss 8.8epss 1.9%
from disclosure to weapon1 days
Published on NVDMay 4
1st PoC+1d
VulnCheck+35d
exploitation probability
1.9%top 22% of all CVEs
observed exploitation
yesVulnCheck
3 public exploit(s)
Ollama before 0.17.1 contains a heap out-of-bounds read vulnerability in the GGUF model loader. The /api/create endpoint accepts an attacker-supplied GGUF file in which the declared tensor offset and size exceed the file's actual length; during quantization in fs/ggml/gguf.go and server/quantization.go (WriteTo()), the server reads past the allocated heap buffer. The leaked memory contents may include environment variables, API keys, system prompts, and concurrent users' conversation data, and can be exfiltrated by uploading the resulting model artifact through the /api/push endpoint to an attacker-controlled registry. The /api/create and /api/push endpoints have no authentication in the upstream distribution. Default deployments bind to 127.0.0.1, but the documented OLLAMA_HOST=0.0.0.0 configuration is widely used in practice (large public-internet exposure observed).
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/V:D/RE:L/U:Red
Affected products
ollama · ollamapublic PoCs found — 3
githubgithub.com/kaleth4/CVE-2026-7482★ 0vulncheckvulncheck.com/xdb/3e5cfd2a36d7unverifiedvulncheckvulncheck.com/xdb/b36f29a426edunverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.