https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 14:24:25 +0000 https://vulnerability.circl.lu/vuln/cve-2026-44564 <p><strong>Affected:</strong> open-webui</p> <p>Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.0, the ydoc:document:update Socket.IO event handler checks whether the sender is a member of the document&#39;s Socket.IO room (line 678) but does not verify that the sender has write permission. Users with read-only access join the document room via ydoc:document:join, which only requires read permission (line 520). Once in the room, the user can emit ydoc:document:update events that modify the in-memory Yjs document state and are broadcast to all other collaborators in real time. This vulnerability is fixed in 0.9.0.</p> <p><strong>Affected:</strong> open-webui</p> <p>Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.0, the ydoc:document:update Socket.IO event handler checks whether the sender is a member of the document&#39;s Socket.IO room (line 678) but does not verify that the sender has write permission. Users with read-only access join the document room via ydoc:document:join, which only requires read permission (line 520). Once in the room, the user can emit ydoc:document:update events that modify the in-memory Yjs document state and are broadcast to all other collaborators in real time. This vulnerability is fixed in 0.9.0.</p> https://vulnerability.circl.lu/vuln/cve-2026-44564 https://vulnerability.circl.lu/vuln/pysec-2026-2762 <p><strong>Affected:</strong> PyPI: open-webui</p> <p># Read-Only Users Can Modify Collaborative Documents via Socket.IO</p> <p>## Affected Component</p> <p>Socket.IO collaborative document editing handler: - `backend/open_webui/socket/main.py` (lines 667-721, `ydoc:document:update` handler)</p> <p>## Affected Versions</p> <p>Current main branch and likely all versions with collaborative note editing.</p> <p>## Description</p> <p>The `ydoc:document:update` Socket.IO event handler checks whether the sender is a member of the document&#39;s Socket.IO room (line 678) but does not verify that the sender has **write** permission. Users with read-only access join the document room via `ydoc:document:join`, which only requires `read` permission (line 520). Once in the room, the user can emit `ydoc:document:update` events that modify the in-memory Yjs document state and are broadcast to all other collaborators in real time.</p> <p>The `document_save_handler` (line 600) correctly checks `write` permission before persisting to the database, so the attacker cannot directly save changes. However, the tampered content is visible to all collaborators, and if any user with write access saves the document, the injected content is persisted.</p> <p>```python # ydoc:document:update handler (line 667) — only checks room membership, not write permission async def on_document_update(sid, data): document_id = normalize_document_id(data.get(&#39;document_id&#39;, &#39;&#39;)) # ... room = f&#39;doc_{document_id}&#39; if room not in sio.rooms(sid): # Room membership check only return # Applies upd…</p> <p><strong>Affected:</strong> PyPI: open-webui</p> <p># Read-Only Users Can Modify Collaborative Documents via Socket.IO</p> <p>## Affected Component</p> <p>Socket.IO collaborative document editing handler: - `backend/open_webui/socket/main.py` (lines 667-721, `ydoc:document:update` handler)</p> <p>## Affected Versions</p> <p>Current main branch and likely all versions with collaborative note editing.</p> <p>## Description</p> <p>The `ydoc:document:update` Socket.IO event handler checks whether the sender is a member of the document&#39;s Socket.IO room (line 678) but does not verify that the sender has **write** permission. Users with read-only access join the document room via `ydoc:document:join`, which only requires `read` permission (line 520). Once in the room, the user can emit `ydoc:document:update` events that modify the in-memory Yjs document state and are broadcast to all other collaborators in real time.</p> <p>The `document_save_handler` (line 600) correctly checks `write` permission before persisting to the database, so the attacker cannot directly save changes. However, the tampered content is visible to all collaborators, and if any user with write access saves the document, the injected content is persisted.</p> <p>```python # ydoc:document:update handler (line 667) — only checks room membership, not write permission async def on_document_update(sid, data): document_id = normalize_document_id(data.get(&#39;document_id&#39;, &#39;&#39;)) # ... room = f&#39;doc_{document_id}&#39; if room not in sio.rooms(sid): # Room membership check only return # Applies upd…</p> https://vulnerability.circl.lu/vuln/pysec-2026-2762