Quick answers
- Is CVE-2026-85180 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85180 being exploited in the wild.
- How severe is CVE-2026-85180?
- High severity, with a CVSS score of 7.5, published 3 September 2026.
- Which products and versions are affected?
- Ollama prior to patch.
- Is there a fix for CVE-2026-85180?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-85180 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85180?
- Check whether you run Ollama at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the blob download logic (x/transfer/download.go) where HTTP redirects are not validated for safety. When pulling tensor-layer models, if a registry serves a specially crafted manifest with redirect responses, the client will follow those redirects to arbitrary hosts without verifying the destination. An unauthenticated attacker who controls or compromises a model registry can exploit this to perform server-side request forgery (SSRF), causing the Ollama server to issue GET requests to internal or cloud metadata endpoints. The attack requires the victim to pull a model from a malicious registry but does not require authentication to the registry itself.
Affected products
- Ollama Ollama prior to patch
Timeline
- 2026-09-03: disclosed