Skip to main content
VulnerabilityPublished Updated

CVE-2026-7482: github.com/ollama/ollama · Ollama contains a heap out-of-bounds read vulnerability in the GGUF model loader

Affects github.com/ollama/ollamaSource GCVE Database

0
Authoritative record:CVE-2026-7482· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.17.1 as a priority.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.17.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade github.com/ollama/ollama to 0.17.1.

Affected software

ProductAffectedFixed in
Gogithub.com/ollama/ollamaAffected
  • <0.17.1
Fixed in
  • 0.17.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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

References

Community reviews

Loading reviews…