CVE-2026-42248
Received Received - Intake
Unsigned Update Execution Vulnerability in Ollama for Windows

Publication date: 2026-04-29

Last updated on: 2026-04-29

Assigner: CERT.PL

Description
Ollama for Windows does not perform integrity or authenticity verification of downloaded update executables. Unlike other platforms, the Windows implementation of the update verification routine unconditionally returns success so no digital signature or trust validation is performed before staging or executing update payloads, enabling attacker‑supplied executables to be accepted and later executed by the application. Critically, Ollama for Windows performs silent automatic updates, so the malicious payload may be installed automatically 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-29
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-04-29
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ollama ollama From 0.12.10 (inc) to 0.17.5 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-494 The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability in Ollama for Windows (CVE-2026-42248) is due to the software not verifying the integrity or authenticity of downloaded update executables. Unlike other platforms, the Windows version's update verification routine always returns success without checking digital signatures or trust. This means attacker-supplied executables can be accepted, staged, and executed by the application.

Additionally, Ollama performs silent automatic updates, so malicious payloads can be installed and executed without the user's knowledge or consent.


How can this vulnerability impact me? :

This vulnerability allows attackers to deliver and execute malicious code on a user's system without their awareness. Because the update process is silent and automatic, users may unknowingly have harmful executables installed and run on their machines.

Such unauthorized code execution can lead to compromise of the affected system, including potential data theft, system manipulation, or further malware installation.


What immediate steps should I take to mitigate this vulnerability?

The vulnerability affects Ollama for Windows versions 0.12.10 through 0.17.5, which perform silent automatic updates without verifying the integrity or authenticity of downloaded update executables.

Immediate mitigation steps include:

  • Avoid using vulnerable versions of Ollama for Windows (0.12.10 through 0.17.5) until a patched version is released.
  • Disable automatic updates in Ollama for Windows if possible, to prevent silent installation of malicious payloads.
  • Monitor and restrict network access to update servers or block update traffic to prevent automatic downloads of potentially malicious executables.
  • Apply additional endpoint protection measures to detect and block execution of unauthorized or suspicious executables.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability in Ollama for Windows allows attacker-supplied executables to be silently installed and executed without user awareness due to lack of integrity and authenticity verification in the update process.

This behavior can lead to unauthorized code execution and potential data breaches, which may violate security requirements mandated by common standards and regulations such as GDPR and HIPAA that require protection of data integrity, confidentiality, and secure software update mechanisms.

Specifically, silent automatic installation of malicious payloads without verification undermines trust in software integrity and could result in unauthorized access or data compromise, thereby impacting compliance with these regulations.


Can you explain this vulnerability to me?

The vulnerability in Ollama for Windows involves the failure to verify the integrity or authenticity of downloaded update executables. Unlike other platforms, the Windows version's update verification routine always returns success without checking digital signatures or trust validation.

This flaw allows attacker-supplied executables to be accepted, staged, and executed by the application. Since Ollama performs silent automatic updates, malicious payloads can be installed and executed without the user's knowledge.


How can this vulnerability impact me? :

This vulnerability can lead to the automatic installation and execution of malicious code on a user's system without their awareness. An attacker can supply malicious update executables that Ollama will accept and run silently.

As a result, the attacker could gain unauthorized control or perform harmful actions on the affected system, potentially compromising data, system integrity, or user privacy.


What immediate steps should I take to mitigate this vulnerability?

Ollama for Windows versions 0.12.10 through 0.17.5 are confirmed vulnerable to this issue where update executables are not verified for integrity or authenticity, allowing attacker-supplied executables to be executed silently.

Immediate mitigation steps include:

  • Avoid using vulnerable versions of Ollama for Windows (0.12.10 to 0.17.5) until a patched version is released.
  • Disable automatic updates in Ollama for Windows to prevent silent installation of malicious payloads.
  • Monitor and restrict network traffic to Ollama update servers to prevent malicious update payloads from being downloaded.
  • Apply additional endpoint protection measures such as application whitelisting and execution prevention for untrusted executables.

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves Ollama for Windows silently installing and executing attacker-supplied update executables without integrity or authenticity verification.

To detect this vulnerability on your system, you can check the installed version of Ollama for Windows to see if it falls within the vulnerable range (versions 0.12.10 through 0.17.5).

  • Run a command to check the Ollama version, for example in PowerShell: `ollama --version` or check the installed program version via Control Panel or Settings.

Additionally, monitoring for unexpected or suspicious executable files in the update staging directories or Windows Startup folder may help detect exploitation attempts.

  • Use PowerShell to list recently modified executables in typical update or startup locations, e.g.: `Get-ChildItem -Path "$env:APPDATA\Microsoft\Windows\Start Menu\Programs\Startup" -Filter *.exe -Recurse | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) }`
  • Monitor network traffic for suspicious downloads or HTTP responses related to Ollama updates, although specific commands for this are not provided.

No specific detection commands are detailed in the provided resources, so detection primarily relies on version checking and monitoring for unexpected executable files or update activity.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart