CVE-2026-42249: 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Ollama for Windowsto a version that resolves this vulnerability.Fixed in 0.17.5 - Compensating control
Because the update mechanism can be abused when an attacker can influence update responses (e.g., via malicious HTTP response headers), ensure update traffic integrity by blocking or preventing man-in-the-middle tampering of Ollama update downloads (e.g., restrict/monitor outbound connections from the host and validate that update sources cannot be altered).
- Operational
After patching/mitigating, review for any executables that may have been written to attacker-chosen locations accessible to the current user (including the Windows Startup directory) and remove any unexpected files; verify persistence is not present.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-42249?
CVE-2026-42249 is classified as a high severity vulnerability due to its potential for remote code execution.
How do I fix CVE-2026-42249?
To fix CVE-2026-42249, users should update Ollama for Windows to version 0.18.0 or later.
What software is affected by CVE-2026-42249?
CVE-2026-42249 affects Ollama for Windows versions 0.12.10 through 0.17.5.
What type of vulnerability is CVE-2026-42249?
CVE-2026-42249 is a remote code execution vulnerability related to the update mechanism.
How can attackers exploit CVE-2026-42249?
Attackers can exploit CVE-2026-42249 by manipulating HTTP response headers when the application downloads updates.