PoC Monitor
← All CVEs
CVE-2026-42249published 29 Apr 2026 11:44 UTCData: JSON · API

Ollama

Remote Code Execution in Ollama via Update Mechanism

Ollama for Windows contains a Remote Code Execution vulnerability in its update mechanism due to improper handling of attacker‑controlled HTTP response headers. When downloading updates, the application constructs local file paths using values derived from HTTP headers without validation. These values are passed directly to filepath.Join, allowing path traversal sequences (../) to be resolved and enabling files to be written outside the intended update staging directory. An attacker who can influence update responses can exploit this flaw to write arbitrary executables to attacker‑chosen locations accessible to the current user, including the Windows Startup directory. This allows execution of arbitrary executables. Critically, when chained with CVE‑2026‑42248 (Missing Signature Verification for Updates), an attacker can deliver malicious payloads that are written to sensitive locations and executed automatically. Because Ollama for Windows performs silent automatic updates and executes staged binaries without user interaction, this results in automatic and persistent code execution without user awareness. Maintainers of this project were notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Versions from 0.12.10 to 0.17.5 were tested and confirmed as vulnerable, other versions were not tested but might also be vulnerable.

First public PoC Date pendingpublic PoC known, its date not yet looked up
Public PoCs10 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS9.8critical · scored by NVD · CWE-494
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Ollama Ollama
  • >= 0.12.10, <= 0.17.5

Mitigation

The record names no fix. Check the vendor advisory below.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published29 Apr 2026 · t = 0

Public PoC known, its date not yet looked up; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.