open-webui · Open WebUI · published 2026-06-23
CVE-2026-54006Open WebUI: Calendar event re-parenting allows writing events into another user's calendar
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-54006 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 23% of all CVEs. This Open WebUI vulnerability: CVSS 4.3 (v3.1). Fixed upstream in Open WebUI 0.9.6, 0.8.11. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Open WebUI 0.9.6, 0.8.11.
Patch events
AI toolingOpen WebUI
Open WebUI security releases: 0.9.6, 0.8.11
Upgrade to
0.9.60.8.11Why: CVE-2026-54011: 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.3% (23th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.3 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N | 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.6(affected)
Description (from the CVE record)#
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.6, POST /api/v1/calendars/events/{event_id}/update validates that the caller has write access to the calendar the event currently belongs to, but does not validate the destination calendar_id supplied in the request body. The model layer then persists the new calendar_id unconditionally. A regular user-role account can therefore create an event in their own calendar and immediately move it into any other user's calendar whose ID they know — bypassing the authorization check that create_event correctly performs. This vulnerability is fixed in 0.9.6.
Quoted from the CVE Program record.