CVE-2026-42248: Missing Signature Verification for Updates in Ollama

Published Apr 29, 2026
·
Updated

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.

Affected Software

3 affected components
Ollama Ollama for Windows>=0.12.10<=0.17.5
All of the following
Ollama Ollama>=0.12.10<=0.17.5
Microsoft Windows

Event History

Apr 29, 2026
CVE Published
via MITRE·11:44 AM
Data Sourced
via MITRE·11:44 AM
DescriptionWeakness
Data Sourced
via NVD·12:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-42248?

CVE-2026-42248 is considered a high-severity vulnerability due to the absence of signature verification for downloaded updates.

2

How do I fix CVE-2026-42248?

To mitigate CVE-2026-42248, ensure that you only obtain updates from trusted sources and apply any available patches from Ollama.

3

What are the potential risks associated with CVE-2026-42248?

The risks associated with CVE-2026-42248 include the possibility of executing malicious code from unverified update executables.

4

Which versions of Ollama for Windows are affected by CVE-2026-42248?

CVE-2026-42248 affects versions of Ollama for Windows from 0.12.10 to 0.17.5.

5

Is there a workaround for CVE-2026-42248?

Currently, the best workaround for CVE-2026-42248 is to manually verify the integrity of updates before installation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203