Ollama Server Vulnerable to Denial of Service (DoS) Attack
CVE-2025-1975 · GHSA-wrh5-cmwx-q2qr · published 2025-05-16 · updated 2026-06-06
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 0.53%
- Fixed in
- No fix yet
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
A vulnerability in the Ollama server version 0.5.11 allows a malicious user to cause a Denial of Service (DoS) attack by customizing the manifest content and spoofing a service. This is due to improper validation of array index access when downloading a model via the /api/pull endpoint, which can lead to a server crash.
No fixed release is listed yet for github.com/ollama/ollama. Limit what it can reach, or stop using it until a fix ships, and follow the source advisory for updates.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| github.com/ollama/ollama | Go | <= 0.5.11 | No fix yet |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalOllama Platform has missing authentication enabling attackers to perform model management operationsgithub.com/ollama/ollama
- HighOllama contains a heap out-of-bounds read vulnerability in the GGUF model loadergithub.com/ollama/ollama
- HighOllama Divide by Zero Vulnerabilitygithub.com/ollama/ollama
- HighOllama Allows Out-of-Bounds Readgithub.com/ollama/ollama
- HighOllama Divide By Zero vulnerabilitygithub.com/ollama/ollama
- HighOllama Allocation of Resources Without Limits or Throttling vulnerabilitygithub.com/ollama/ollama
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.