# CVE-2025-44779: Ollama allows deletion of arbitrary files

> Attackers can delete arbitrary files on the server by sending crafted packets to the /api/pull endpoint in Ollama.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Aug 2025
- **Updated:** 7 Aug 2025
- **Also known as:** GHSA-93jv-pvg8-hf3v, GO-2025-3851

## What is CVE-2025-44779?

CVE-2025-44779 is a medium-severity path traversal vulnerability in n/a, published on 7 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue in Ollama v0.1.33 allows attackers to delete arbitrary files via sending a crafted packet to the endpoint /api/pull.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-44779?

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 | 0.1.34 |
| `github.com/ollama/ollama` | Go | All versions | 0.1.34 |
| `github.com/ollama/ollama` | Go | All versions | 0.1.34 |

Products: Ollama Ollama.

## How do I fix CVE-2025-44779?

Upgrade github.com/ollama/ollama to 0.1.34 or later.

## Is CVE-2025-44779 being exploited?

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

## Other vulnerabilities in n/a

- [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-2025-44779 and fix it if it is affected.

What it is: CVE-2025-44779 is a medium-severity path traversal vulnerability in n/a, published on 7 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44779 exists.

Affected packages and fixed versions:
- github.com/ollama/ollama (Go): affected all versions; fixed in 0.1.34
- github.com/ollama/ollama (Go): affected all versions; fixed in 0.1.34
- github.com/ollama/ollama (Go): affected all versions; fixed in 0.1.34

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

## Sources

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

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