GHSA-gmfw-g93r-vg53: Open WebUI: Unauthenticated WebSocket Access to Collaborative Document Handlers (ydoc:awareness:update, ydoc:document:leave)

Summary

Open WebUI's Socket.IO server is configured with `always_connect=True` in `backend/open_webui/socket/main.py`, and its `connect` handler never rejects unauthenticated connections. The Ydoc handlers `ydoc:awareness:update` and `ydoc:document:leave` perform no authentication or room membership checks. An unauthenticated attacker can therefore spoof any `user_id` and inject fake awareness data into a document room, or broadcast fake `ydoc:user:left` events. The report also notes unlimited unauthenticated WebSocket connections as a resource exhaustion impact.

Mitigation

1. Set `always_connect=False` or reject unauthenticated connections in the `connect` handler 2. Add `SESSION_POOL` checks to `ydoc:awareness:update` and `ydoc:document:leave` 3. Add room membership verification before broadcasting to document rooms

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

• open-webuiPyPILLM dependency since 2024-05-20

Related items

• MediumCVE-2026-121936: easyVoice server-side request forgery through openaiBaseUrl in /api/v1/ttsSimilar attack · NVD/CVE Database
• MediumCVE-2026-118628: MLflow get-artifacts server-side request forgery information disclosureSimilar attack · NVD/CVE Database
• HighCVE-2026-118625: MLflow Tracking Server privilege escalation via get_endpointsSimilar attack · NVD/CVE Database
• InfoWhen trust becomes the payload: Inside the threats, etc quarterly reportSimilar attack · Elastic Security Labs
• MediumCritical Langflow flaws enable authentication bypass and RCESimilar attack · CSO Online