NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · Ollama

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

mediumCVSS 3.1 6.6GHSA-93jv-pvg8-hf3v

Ollama 0.1.33 and earlier can be made to delete arbitrary files on the server through a crafted `POST /api/pull` request that points at an attacker-controlled registry. During the save step, Ollama deletes any existing file at the path where a layer digest is to be stored. Fixed in Ollama 0.1.34.

Published Aug 7, 2025 · Analysis Nov 1, 2026

What an attacker can do

/api/pull accepts a model name that names a self-hosted registry, and an insecure flag. Ollama fetches the manifest from that registry, then walks the layers digests, downloads and verifies each, and saves it. The write-up explains that when a file already exists at the path where a digest is to be saved, Ollama reports a digest mismatch and deletes the existing file.

An attacker who can reach the Ollama API sends a pull for a model on their own server. That server returns a manifest that steers the save step toward a victim file, and Ollama removes it. The write-up does not fully explain how the target path is chosen. The proof of concept deletes a file created on the server. The loss is integrity and availability: model files, config or any file the Ollama process can write could be destroyed, and the service may stop working. The CVSS vector lists local access and user interaction, which is stricter than the exposure of a default network listener, so treat any network-reachable Ollama as at risk.

Who is affected

Ollama 0.1.33 and earlier. Check the version on the server:

ollama --version
go list -m github.com/ollama/ollama

go list applies to Go projects that import Ollama as a module. Servers whose API port (11434 by default) is reachable from untrusted hosts, including containers with that port published, are the ones to prioritize.

github.com/ollama/ollama

Ecosystem
Go
Affected
< 0.1.34
Fixed in
0.1.34
Check
go list -m github.com/ollama/ollama

How to fix it

Upgrade to Ollama 0.1.34 or later. Download the current release from the project, or pull the latest Docker image:

docker pull ollama/ollama:latest

The sources do not describe the code change. They give no workaround. Until you upgrade, do not expose the API to untrusted networks, and block unneeded outbound connections from the server so it cannot reach an attacker's registry.

How to tell if you were hit

Check the Ollama server log for /api/pull requests whose model name starts with an unfamiliar host or IP, and for requests with insecure set to true. Look for digest mismatch errors in the log, which appear when the save step meets an existing file. Check for model blobs or other files that have gone missing, and for outbound connections from the server to unknown registries.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

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

Questions

Which Ollama version fixes CVE-2025-44779?

0.1.34. The researcher's write-up says versions up to 0.1.33 are affected and 0.1.34 or later is fixed.

What does the attacker control?

A malicious registry. The crafted pull request points at it, and its manifest drives Ollama's save step to a victim path, where an existing file is deleted.

Is there a public proof of concept?

Yes. The researcher's write-up lists steps: create a target file, run a fake registry serving the crafted manifest, send the pull request, and confirm the file is deleted. The sources do not report attacks in the wild.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More Ollama vulnerabilities

All Ollama entries