# Ollama vulnerable to Cross-Domain Token Exposure

Advisory record · `GHSA-x9hg-5q6g-q3jr`

- **Identifiers:** `GHSA-x9hg-5q6g-q3jr` · `CVE-2025-51471` · `GO-2025-3824` · `PYSEC-2025-147`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html) · [CWE-384](https://cwe.mitre.org/data/definitions/384.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md)
- **Published:** 22 Jul 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Jul 2025, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/ollama/ollama` (Go): affected `<=0.9.6`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Ollama (Go module github.com/ollama/ollama) versions up to and including 0.9.6 are affected. A remote attacker who can get Ollama to pull from a server they control, such as through the /api/pull endpoint, can supply a malicious realm value in a WWW-Authenticate header and cause Ollama to send authentication tokens to that realm, which can allow access control bypass. No fixed version is listed.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.19, the 97th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x9hg-5q6g-q3jr)

## Sources

- [GitHub Advisory Database: GHSA-x9hg-5q6g-q3jr](https://github.com/advisories/GHSA-x9hg-5q6g-q3jr)
- [OSV: GHSA-x9hg-5q6g-q3jr](https://osv.dev/vulnerability/GHSA-x9hg-5q6g-q3jr)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-51471>
- <https://github.com/ollama/ollama/pull/10750>
- <https://github.com/ollama/ollama>
- <https://github.com/pypa/advisory-database/tree/main/vulns/ollama/PYSEC-2025-147.yaml>
- <https://huntr.com/bounties/94eea285-fd65-4e01-a035-f533575ebdc2>
- <https://www.gecko.security/blog/cve-2025-51471>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x9hg-5q6g-q3jr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x9hg-5q6g-q3jr/>. Everything for agents: <https://agentprime.io/llms.txt>.