Skip to content
AI/ML

CVE-2026-65315

8.7
High
EPSS 0.81%Jul 23, 2026

Uncontrolled memory allocation in Ollama GGUF parser allows remote crash via crafted model file

common questions

Is CVE-2026-65315 being exploited?

Not confirmed. CVE-2026-65315 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.81% probability of exploitation in the next 30 days.

How severe is CVE-2026-65315?

CVE-2026-65315 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-65315?

Not known from our data. No patch reference has been recorded for CVE-2026-65315, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-65315 affect?

CVE-2026-65315 affects Ollama server (GGUF parser), Model blob upload API, Model create/pull API endpoints. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-65315?

Block untrusted uploads, restrict API access, deploy vendor patch when released

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Ollama server (GGUF parser)Model blob upload APIModel create/pull API endpoints
impact

Remote denial-of-service: crafted GGUF upload (sub-1KB) triggers Go OOM or makeslice panic, crashing the server process.

action required

Immediate action required

affected versions
Ollama Ollama
  • affected<= f0078ae

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free