CVSS 4.0
8.8 highCVSS: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:RedKnown as Bleeding Llama
High (8.8) in ollama ollama. EPSS 7.1% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/ollama/ollama 0.17.1.
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:RedCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Hgithub.com/ollama/ollama (Go): fixed in 0.17.1Explain CVE-2026-7482 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7482?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7482?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-7482 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| ollama | before 0.17.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-x8qc-fggm-mpqg | Go | github.com/ollama/ollama | <0.17.1 | 0.17.1 |
| GO-2026-5748 | Go | github.com/ollama/ollama | <0.17.1 | 0.17.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | govulncheck-vulndb | 0.0.20260727T201416-160000.1.1 | SUSE-SU-2026:23216-1 SUSE-SU-2026:23227-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260727T201416-160000.1.1 | openSUSE-SU-2026:21551-1 |
| openSUSE | Tumbleweed | ollama | 0.33.1-1.1 | openSUSE-SU-2026:11688-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.
Red Hat rates this Critical.
An Important information disclosure flaw exists in Ollama, allowing a remote, unauthenticated attacker to read heap memory via a crafted GGUF file submitted to the /api/create endpoint. This can expose sensitive data, including API keys and user conversation data, which can then be exfiltrated. While default deployments bind to localhost, configurations exposing Ollama to the public internet significantly increase the risk.
In this flaw a network attacker may leak sensitive data (C:H, I:N) with limited scope of system denial of servci (A:L), where a system reboot may not be the scenario.
| Product | Package | State | Advisory |
|---|---|---|---|
| Migration Toolkit for Applications 8 | mta/mta-solution-server-rhel9 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-24/lightspeed-rhel8 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-25/lightspeed-rhel8 | Not affected | |
| Red Hat build of Debezium 3 | debezium-ai-embeddings-ollama | Not affected | |
| Red Hat build of Debezium 3 | langchain4j-ollama | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9 | Not affected | |
| Red Hat Trusted Profile Analyzer | rhtpa/rhtpa-trustification-service-rhel9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-7482.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.