Ollama vulnerable to Cross-Domain Token Exposure in github.com/ollama/ollama (CVE-2025-51471)

Ollama vulnerable to Cross-Domain Token Exposure in github.com/ollama/ollama (CVE-2025-51471) | HOL Guard CVE

Why this deserves its current priority

CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/ollama/ollama (go), github.com/ollama/ollama (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/ollama/ollamago	<=0.9.6	Not reported
github.com/ollama/ollamago	>=0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/ollama/ollama, github.com/ollama/ollama.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Jul 22, 2025
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Jun 11, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.