Quick answers
- Is CVE-2026-65315 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65315 being exploited in the wild.
- How severe is CVE-2026-65315?
- High severity, with a CVSS score of 7.5, published 21 July 2026.
- Which products and versions are affected?
- Ollama up to commit f0078ae.
- Is there a fix for CVE-2026-65315?
- 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-65315 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-65315?
- Check whether you run Ollama 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
An uncontrolled memory allocation vulnerability (CWE-789) exists in Ollama's GGUF metadata parser within `fs/ggml/gguf.go`. The parser reads length and count fields (string lengths, tensor dimension counts, and metadata array counts) directly from GGUF files and uses them as allocation sizes for `make()` calls or slice bounds without validating them against the actual file size. A remote, unauthenticated attacker can trigger this by uploading a sub-1KB crafted GGUF file via the `/api/blobs` and `/api/create` endpoints, or by inducing a model pull. This results in Go runtime fatal errors (out-of-memory) or `makeslice` panics that bypass standard recovery middleware, causing a complete process crash. The vulnerability affects versions up to commit f0078ae.
Affected products
- Ollama Ollama up to commit f0078ae
Timeline
- 2026-06-03: disclosed: Reported via Huntr
- 2026-07-05: other: Public GitHub issue opened
- 2026-07-21: advisory: NVD publication date