open-webui · Open WebUI · published 2026-08-04
CVE-2026-70489Open WebUI: Instance-wide stall via automation recurrence rules that force multi-second parsing
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-70489 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 48% of all CVEs. This Open WebUI vulnerability: CVSS 6.5 (v3.1). Fixed upstream in Open WebUI 0.11.0. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Open WebUI 0.11.0.
Patch events
AI toolingOpen WebUI
Open WebUI security release: 0.11.0
Upgrade to
0.11.0Why: CVE-2026-70492: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.6% (48th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- open-webui open-webui
>= 0.9.0, < 0.11.0(affected)
Description (from the CVE record)#
Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.0 until 0.11.0, automation recurrence parsing in backend/open_webui/utils/automations.py anchored minutely and hourly rules at a fixed date of 2000-01-01 and then walked forward one interval at a time to find the next run. A single FREQ=MINUTELY rule enumerates roughly a quarter-century of occurrences synchronously on the event loop that also serves scheduler, HTTP, and WebSocket traffic, and the scheduler recomputes the next run for every claimed row on each poll. This causes availability impact for every other user of the instance. This issue is fixed in 0.11.0.
Quoted from the CVE Program record.