← Back to Vulnerability Reports CVE Intelligence

CVE-2026-7482

Ollama•CRITICAL · CVSS 9.1•No exploitation reported

What is CVE-2026-7482?

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).

CVSS9.1 NVD 3.1
SeverityCRITICAL
ExploitationNo exploitation reported
EPSS1% · P53
Triage statusNo Known Exploit
ActionPatch within 48 hours
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CWECWE-125
NVD published2026-05-04
NVD last modified2026-06-17

Timeline

  • 2026-05-04Published to the U.S. National Vulnerability Database (NVD)
  • 2026-06-17NVD record last updated

Affected product

Ollama

Remediation Steps

  1. Immediately disconnect or isolate affected Ollama instances from untrusted networks
  2. Update Ollama to the latest patched version released by the project
  3. Review server logs for evidence of unauthorized memory access or exfiltration
  4. Rotate all credentials and secrets that may have been exposed in process memory
  5. Implement network-level access controls restricting Ollama API access

Referenced in our briefings & reports

Related vulnerabilities

Browse all tracked CVEs in the defend.network CVE database →

🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.