Quick answers
- Is CVE-2026-15685 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15685 being exploited in the wild.
- How severe is CVE-2026-15685?
- High severity, with a CVSS score of 7.5, published 13 July 2026.
- Which products and versions are affected?
- Ollama 0.7.1; ollama (PyPI) ECOSYSTEM:introduced=0,last_affected=0.7.1-NA.
- Is there a fix for CVE-2026-15685?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-15685 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-15685?
- Check whether you run Ollama or ollama (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A denial-of-service vulnerability exists in Ollama due to improper validation of an array index within the downloadBlob function (CWE-129). The flaw is triggered when the application processes user-supplied data that lacks adequate bounds checking, leading to an out-of-bounds memory access. A remote, unauthenticated attacker can exploit this by sending a malicious request to the affected service, causing the process to crash. As of the advisory date, no official patch was confirmed, and the recommended mitigation is to restrict network access to the Ollama API.
Affected products
- Ollama Ollama 0.7.1
Identifiers
- CVE-2026-15685
- PYSEC-2026-3450
Timeline
- 2025-05-28: disclosed: Vulnerability reported to vendor by ZDI
- 2026-07-08: advisory: Coordinated public release of advisory by ZDI
- 2026-07-13: other: NVD publication date