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).
The record classifies CVE-2026-7482 under weakness class CWE-125. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 154 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 9.1 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H - CVSS v4.0 base score
- 8.8
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 - EPSS (FIRST)
- 1.0% probability of exploitation in the next 30 days, higher than 58.5% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 6.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-05-04
Is CVE-2026-7482 being exploited?
No public exploitation evidence for CVE-2026-7482 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-05-04. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.
Affected products and versions
- ollama: ollama
Affected software packages:
go:github.com/ollama/ollama— patched in 0.17.1
How to fix CVE-2026-7482
The record marks a vendor fix as available for CVE-2026-7482. Fixed versions are recorded for 1 package: go:github.com/ollama/ollama 0.17.1. Patch reference: https://github.com/ollama/ollama/commit/88d57d0483cca907e0b23a968c83627a20b21047. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-7482
1 tracked threat in the Threadlinqs corpus references CVE-2026-7482, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.