open-webui · Open WebUI · published 2026-09-09
CVE-2026-87015Open WebUI: A user's session cookies are sent to tool servers configured for bearer authentication
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-87015 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 42% of all CVEs. This Open WebUI vulnerability: CVSS 6.8 (v3.1), a successful attack gives total control of the component. Fixed upstream in Open WebUI 0.11.1. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Open WebUI 0.11.1.
Patch events
AI toolingOpen WebUI
Open WebUI security release: 0.11.1
Upgrade to
0.11.1Why: CVE-2026-87016: 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.5% (42th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.8 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- open-webui open-webui
>= 0.6.27, < 0.11.1(affected)
Description (from the CVE record)#
Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.6.27 until 0.11.1, backend/open_webui/utils/tools.py captured a cookie jar from the enclosing connection loop instead of binding it to each external tool callable. When multiple tool servers were attached and a session or system OAuth connection was processed last, a request to a different server configured for bearer authentication could include the calling user's Open WebUI session cookies, allowing that server's operator to reuse the session and take over the account. This issue is fixed in version 0.11.1.
Quoted from the CVE Program record.