# CVE-2026-7020: Ollama Tensor Model Transfer transfer.go digestToPath path traversal

> Remote attackers can exploit a path traversal flaw in Ollama's tensor model transfer to read or modify files, requiring high complexity.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Apr 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-x99g-8v8j-25j2, GO-2026-5750, MINI-3xqh-w656-wmp7, MINI-x368-6cp9-mfw9

## What is CVE-2026-7020?

CVE-2026-7020 is a medium-severity path traversal vulnerability in Ollama, published on 26 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in Ollama up to 0.20.2. This affects the function digestToPath of the file x/imagegen/transfer/transfer.go of the component Tensor Model Transfer Handler. The manipulation of the argument digest results in path traversal. The attack may be performed from remote. This attack is characterized by high complexity. The exploitability is reported as difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/ollama/ollama. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ollama/ollama` | Go | All versions | None |
| `github.com/ollama/ollama` | Go | All versions to 0.20.2 | None |
| `github.com/ollama/ollama` | Go | All versions to 0.20.2 | None |

Products: Ollama Ollama.

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

Upgrade to a fixed version.

## Is CVE-2026-7020 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7020 exists.

Public exploit code:

- POC for CVE-2026-7720 - Ollama tensor digest path traversal  (github_poc): https://github.com/davidrxchester/CVE-2026-7020

## Other vulnerabilities in Ollama

- [CVE-2025-63389](https://insights.sbomify.com/CVE-2025-63389/): Ollama Platform has missing authentication enabling attackers to perform model management operations (critical 9.8)
- [CVE-2024-45436](https://insights.sbomify.com/CVE-2024-45436/): Ollama can extract members of a ZIP archive outside of the parent directory (critical 9.1)
- [CVE-2026-7482](https://insights.sbomify.com/CVE-2026-7482/): Ollama heap out-of-bounds read in GGUF tensor parsing leaks server process memory to unauthenticated remote attackers (high 8.8)
- [CVE-2024-37032](https://insights.sbomify.com/CVE-2024-37032/): Ollama does not validate the format of the digest (sha256 with 64 hex digits) (high 8.8)
- [CVE-2025-15514](https://insights.sbomify.com/CVE-2025-15514/): Ollama Multi-Modal Model Image Processing NULL Pointer Dereference (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7020 is a medium-severity path traversal vulnerability in Ollama, published on 26 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7020 exists.

Affected packages and fixed versions:
- github.com/ollama/ollama (Go): affected all versions; no fix listed
- github.com/ollama/ollama (Go): affected all versions up to 0.20.2; no fix listed
- github.com/ollama/ollama (Go): affected all versions up to 0.20.2; no fix listed

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-7020/ (Markdown: https://insights.sbomify.com/CVE-2026-7020/index.md)
```

## Sources

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

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