# CVE-2026-85180: Ollama 0.30.0 through 0.33.2 SSRF via Cross-Host Tensor Blob Redirect

> Unauthenticated attackers can force Ollama to fetch data from internal hosts or cloud metadata endpoints via malicious model manifests.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-57p7-34ff-7w3w, MINI-26j3-3v75-9g3r, MINI-w8qh-4ffj-jfqh

## What is CVE-2026-85180?

CVE-2026-85180 is a high-severity server-side request forgery vulnerability in ollama, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ollama fails to validate redirect destinations when pulling tensor-layer models, allowing unauthenticated attackers to redirect blob downloads to arbitrary hosts. An attacker can control a registry, serve a malicious tensor-layer manifest, and cause the server to issue GET requests to internal hosts including cloud metadata endpoints.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-85180?


## How do I fix CVE-2026-85180?

Upgrade to a fixed version.

## Is CVE-2026-85180 being exploited?

There is no known exploitation of CVE-2026-85180 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85180 and fix it if it is affected.

What it is: CVE-2026-85180 is a high-severity server-side request forgery vulnerability in ollama, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85180 in the wild and no public exploit code.

Affected product: ollama. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85180/ (Markdown: https://insights.sbomify.com/CVE-2026-85180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85180
- OSV: https://osv.dev/vulnerability/CVE-2026-85180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85180/
Summaries are generated and may contain mistakes; the official description above is the record.