CVE-2026-42248: Ollama for Windows missing update signature verification
Ollama
Ollama for Windows lacks integrity checks for downloaded update executables, allowing malicious updates to be executed. The vulnerability affects the automatic update routine without requiring user interaction.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.8
- EPSS
- 0.01 · top 46% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 29 Apr 2026
- last update
- 29 Apr 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-04-29CVE-2026-42248: Ollama for Windows does not perform integrity or authenticity verification of downloaded update executables.NVD · nvd.nist.gov/vuln/detail/CVE-2026-42248
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 29 Apr 2026 · first reported 29 Apr 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-42248: Ollama for Windows missing update signature verification https://gcdradar.vercel.app/incidents/cve-2026-42248-ollama-for-windows-missing-update-signature-v · AIR-2026-1051 · closed 2026-04-29 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-04-29 - AI role: Attack on AI - Products: Ollama - CVE ids: CVE-2026-42248 - CVSS: 9.8 ## Summary Ollama for Windows lacks integrity checks for downloaded update executables, allowing malicious updates to be executed. The vulnerability affects the automatic update routine without requiring user interaction. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-04-29: CVE-2026-42248: Ollama for Windows does not perform integrity or authenticity verification of downloaded update executables. (https://nvd.nist.gov/vuln/detail/CVE-2026-42248) ## Sources - 2026-04-29 NVD: CVE-2026-42248: Ollama for Windows does not perform integrity or authenticity verification of downloaded update executables. https://nvd.nist.gov/vuln/detail/CVE-2026-42248 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed5.4Open WebUI CVE-2026-44563: Open WebUI Ollama Model Access Control Bypass
Patch now · Disclosed · since 8 May 2026 · updated 15 May 2026 · CVE-2026-44563
AI - closed9.1Ollama CVE-2026-7482: Ollama heap out-of-bounds read in GGUF model loader
Patch now · Disclosed · since 4 May 2026 · CVE-2026-7482
AI - closed9.8Ollama CVE-2026-42249: Ollama for Windows update mechanism remote code execution
Patch now · Disclosed · since 29 Apr 2026 · CVE-2026-42249
AI - closed5.6Ollama CVE-2026-7020: Ollama Path Traversal Vulnerability
Patch now · Disclosed · since 26 Apr 2026 · CVE-2026-7020
AI - closed6.3Ollama CVE-2026-5530: Server-side request forgery flaw found in Ollama
Patch now · Disclosed · since 5 Apr 2026 · CVE-2026-5530
AI - closed7.3Ollama CVE-2026-108836: Server-side request forgery in Ollama pull API
Patch now · Disclosed · since 12 Oct 2026 · CVE-2026-108836
AI