# CVE-2025-0315: Allocation of Resources Without Limits or Throttling in ollama/ollama

> A malicious user can upload a crafted model file to the Ollama server, causing unlimited memory allocation and resulting in a Denial of Service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-fccc-8m69-8r78, GO-2025-3557, MINI-4hh3-rwh4-2589, MINI-5fm7-5wq3-3949

## What is CVE-2025-0315?

CVE-2025-0315 is a high-severity denial of service vulnerability in ollama/ollama, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in ollama/ollama <=0.3.14 allows a malicious user to create a customized GGUF model file, upload it to the Ollama server, and create it. This can cause the server to allocate unlimited memory, leading to a Denial of Service (DoS) attack.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

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.3.14 | None |
| `github.com/ollama/ollama` | Go | All versions to 0.3.14 | None |

Products: Ollama Ollama.

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

Upgrade to a fixed version.

## Is CVE-2025-0315 being exploited?

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

## Other vulnerabilities in ollama/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-2025-0315 and fix it if it is affected.

What it is: CVE-2025-0315 is a high-severity denial of service vulnerability in ollama/ollama, published on 20 Mar 2025. 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-2025-0315 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.3.14; no fix listed
- github.com/ollama/ollama (Go): affected all versions up to 0.3.14; 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-2025-0315/ (Markdown: https://insights.sbomify.com/CVE-2025-0315/index.md)
```

## Sources

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

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