CVE-2026-7482
Heap OOB read in Ollama GGUF loader allows data leakage via unauthenticated API.
Is CVE-2026-7482 being exploited?
Not confirmed. CVE-2026-7482 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-7482?
CVE-2026-7482 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-7482?
Yes. A fix has been recorded for CVE-2026-7482. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-7482 affect?
CVE-2026-7482 affects Ollama <= 0.17.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-7482?
Upgrade to 0.17.1+; enable auth; restrict exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Exfiltrates memory data (env vars, API keys, prompts, chats) via crafted GGUF through /api/create; no auth.
Patch when possible
- affected< 0.17.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.