Ollama (HEAD f0078ae) contains an uncontrolled memory allocation vulnerability in the GGUF metadata parser that allows remote attackers to crash the server by supplying a crafted GGUF file with attacker-controlled length and count fields in string lengths, tensor dimension counts, and metadata array counts that are used as allocation sizes without validation against remaining file size. Attackers can upload a sub-1KB crafted GGUF file via the blob upload and model create or pull API endpoints to trigger unrecoverable Go runtime out-of-memory fatal errors or makeslice panics that bypass recovery middleware and crash the entire server process.
CVE-2026-65315
This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EPSS
- 43.8%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Jul 22, 2026Ollama Remote Denial of Service via Attacker-Controlled Allocation in GGUF Metadata Parser | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ollama-remote-denial-of-service-via-attacker-controlled-allocation-in-gguf-metadata-parserGitHub - ollama/ollama: Get up and running with Kimi-K2.6, GLM-5.2, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models. · GitHub
https://github.com/ollama/ollamaUnbounded / attacker-controlled memory allocation in the GGUF metadata parser → remote denial of service (unrecoverable server crash) from a tiny crafted model file · Issue #17042 · ollama/ollama · GitHub
https://github.com/ollama/ollama/issues/17042Vendor Advisories for CVE-2026-65315(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 23:11 UTCEG score recompute
- 2026-07-21 21:38 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-65315?
When was CVE-2026-65315 disclosed?
Is CVE-2026-65315 actively exploited?
What is the CVSS score of CVE-2026-65315?
How do I remediate CVE-2026-65315?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65315
Is Your Infrastructure Affected by CVE-2026-65315?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.