Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.6.16 before 0.10.0, the Socket.IO server is configured with always_connect=True. The ydoc:awareness:update and ydoc:document:leave Socket.IO handlers accepted collaborative-document events without requiring an authenticated user, allowing unauthorized manipulation of document collaboration state. This issue is fixed in version 0.10.0.
CVE-2026-59715
This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EPSS
- 12.7%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 10, 2026Unauthenticated WebSocket Access to Collaborative Document Handlers (ydoc:awareness:update, ydoc:document:leave) · Advisory · open-webui/open-webui · GitHub
https://github.com/open-webui/open-webui/security/advisories/GHSA-gmfw-g93r-vg53v0.10.0
Patch available: open-webui/open-webui v0.10.0
https://github.com/open-webui/open-webui/releases/tag/v0.10.0Require auth on ydoc:awareness:update and ydoc:document:leave handler
Fix merged in open-webui/open-webui PR #25946 on 2026-06-16 — awaiting tagged release
https://github.com/open-webui/open-webui/pull/25946commit 22f2fe1ffb66 (open-webui/open-webui)
Fix landed in open-webui/open-webui commit 22f2fe1ffb66 — awaiting tagged release
https://github.com/open-webui/open-webui/commit/22f2fe1ffb66c993dad1e0b2b35514acaed2370eWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 20:20 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 18:28 UTCEG score recompute▲ 3.40
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 02:46 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
- 2026-07-09 16:28 UTCEG score recompute
- 2026-07-09 16:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS 91%CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS 97%CRITICAL
- CVE-2018-25134EG 9.8CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2018-21132EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
- CVE-2006-0061EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-59715?
When was CVE-2026-59715 disclosed?
Is CVE-2026-59715 actively exploited?
What is the CVSS score of CVE-2026-59715?
How do I remediate CVE-2026-59715?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59715
Is Your Infrastructure Affected by CVE-2026-59715?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.