Loading vulnerability…
CVE-2025-51471 is a cross-domain authentication-token exposure vulnerability in Ollama 0.6.7. The server.auth.getAuthorizationToken logic can improperly handle a malicious realm value supplied in a WWW-Authenticate response header from a remote endpoint contacted through the /api/pull API. This may cause Ollama to disclose an authentication token to an attacker-controlled realm, violating authentication-domain boundaries.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a Proof of Concept (PoC) exploit for CVE-2025-51471, a cross-domain authentication token exposure vulnerability affecting all versions of Ollama. The repository contains two files: a detailed README.md explaining the vulnerability, impact, and usage, and a Python script (malicious_registry.py) that implements a malicious registry server using Flask. The exploit works by running the server and tricking a victim into pulling a model from the attacker's registry. The server responds with a 401 Unauthorized and a WWW-Authenticate header pointing to an attacker-controlled endpoint. Ollama, due to improper domain validation, sends its Ed25519 signed authentication token to the attacker's server, which is then captured and logged. The script provides endpoints for triggering the exploit, capturing tokens, and viewing the captured tokens. The exploit is a network-based attack and does not require local access. The PoC is operational and demonstrates the vulnerability, but does not include weaponized payloads beyond token capture.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.