# CVE-2025-51471: Ollama vulnerable to Cross-Domain Token Exposure

> Remote attackers can steal authentication tokens via a malicious realm value, enabling access control bypass and data exposure in Ollama.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Jul 2025
- **Updated:** 17 Oct 2025
- **Also known as:** CLEANSTART-2026-OA88832, GHSA-x9hg-5q6g-q3jr, GO-2025-3824, MINI-265x-xh5q-74hg

## What is CVE-2025-51471?

CVE-2025-51471 is a medium-severity vulnerability in n/a, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-384 (Session Fixation), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2025-51471?

3 open source packages ship an affected version, including github.com/ollama/ollama. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ollama/ollama` | Go | All versions | None |
| `github.com/ollama/ollama` | Go | All versions to 0.9.6 | None |
| `github.com/ollama/ollama` | Go | All versions to 0.9.6 | None |

Products: Ollama Ollama.

## How do I fix CVE-2025-51471?

Upgrade to a fixed version.

## Is CVE-2025-51471 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51471 exists.

Public exploit code:

- This PoC is for educational and authorized security testing purposes only. Do NOT use against systems you don't own. (github_poc): https://github.com/ajtazer/CVE-2025-51471-POC

## Other vulnerabilities in n/a

- [CVE-2025-63389](https://insights.sbomify.com/CVE-2025-63389/): Ollama Platform has missing authentication enabling attackers to perform model management operations (critical 9.8)
- [CVE-2024-45436](https://insights.sbomify.com/CVE-2024-45436/): Ollama can extract members of a ZIP archive outside of the parent directory (critical 9.1)
- [CVE-2026-7482](https://insights.sbomify.com/CVE-2026-7482/): Ollama heap out-of-bounds read in GGUF tensor parsing leaks server process memory to unauthenticated remote attackers (high 8.8)
- [CVE-2024-37032](https://insights.sbomify.com/CVE-2024-37032/): Ollama does not validate the format of the digest (sha256 with 64 hex digits) (high 8.8)
- [CVE-2025-15514](https://insights.sbomify.com/CVE-2025-15514/): Ollama Multi-Modal Model Image Processing NULL Pointer Dereference (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-51471 and fix it if it is affected.

What it is: CVE-2025-51471 is a medium-severity vulnerability in n/a, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51471 exists.

Affected packages and fixed versions:
- github.com/ollama/ollama (Go): affected all versions; no fix listed
- github.com/ollama/ollama (Go): affected all versions up to 0.9.6; no fix listed
- github.com/ollama/ollama (Go): affected all versions up to 0.9.6; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-51471/ (Markdown: https://insights.sbomify.com/CVE-2025-51471/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-51471
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-51471
- OSV: https://osv.dev/vulnerability/CVE-2025-51471

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-51471/
Summaries are generated and may contain mistakes; the official description above is the record.