CVE-2025-51471 json
Ollama vulnerable to Cross-Domain Token Exposure
published 2025-07-22 15 mo ago modified 2026-09-10 1 mo ago also GHSA-x9hg-5q6g-q3jr , GO-2025-3824 , PYSEC-2025-147 , EUVD-2025-22351
- cvss
- 6.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.5%
- EPSS 18.5% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Cross-Domain Token Exposure in server.auth.getAuthorizationToken in Ollama 0.6.7 allows remote attackers to steal authentication tokens and bypass access controls via a malicious realm value in a WWW-Authenticate header returned by the /api/pull endpoint.
Patch / fix
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20250730T213748-1.1
opensuse advisories openSUSE-SU-2025:15405-1
- github.com/ollama/ollama#10750 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-51471 updated cvss 3.4
ollama: Ollama token exposure
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 15 mo ago
Exploit prediction
18.53% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/ollama/ollama/pull/10750 referenced PoC, tagged "exploit" by a source, unverified
- gecko.security https://www.gecko.security/blog/cve-2025-51471 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N |
| CNA | 3.1 | 6.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N |
| GitHub | 3.1 | 6.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/ollama/ollama | <=0.9.6 all versions |
no fix listed |
Classification
References
-
github.com
/ollama/ollama/pull/10750
web, exploit, issue-tracking, report, patch
-
gecko.security
/blog/cve-2025-51471
web, exploit, third-party-advisory, evidence
-
github.com
/ollama/ollama
package, product
-
huntr.com
/bounties/94eea285-fd65-4e01-a035-f533575ebdc2
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-51471
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/ollama/PYSEC-2025-147.yaml
web
-
github.com
/advisories/GHSA-x9hg-5q6g-q3jr
advisory
Sources
- CVE List CVE-2025-51471
- GitHub Advisory GHSA-x9hg-5q6g-q3jr
- NVD CVE-2025-51471
- OSV PYSEC-2025-147
- OSV GO-2025-3824
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.