CVE-2025-51471

CVE-2025-51471 is a medium-severity vulnerability in Ollama with a CVSS 3.x base score of 6.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.

Key facts

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.

Frequently asked questions

What is CVE-2025-51471?
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.
How severe is CVE-2025-51471?
CVE-2025-51471 has a CVSS 3.x base score of 6.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity low, and availability none.
Is CVE-2025-51471 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-51471?
CVE-2025-51471 affects Ollama. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-51471?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-51471 have an EU (EUVD) identifier?
Yes. CVE-2025-51471 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-22351.
When was CVE-2025-51471 published?
CVE-2025-51471 was published on 2025-07-22 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ollama

All CVEs affecting Ollama →

Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities

Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →