https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 18 Oct 2026 11:47:06 +0000 https://cve.radiocsirt.org/vuln/cve-2026-44559 <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 GET /api/v1/channels/{id}/members endpoint only checks membership for group and dm channel types (lines 467-469). For standard channels — including private ones — there is no channel_has_access check before returning the member list. Any authenticated user who knows a private channel&#39;s UUID can enumerate all users with access to that channel. 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 GET /api/v1/channels/{id}/members endpoint only checks membership for group and dm channel types (lines 467-469). For standard channels — including private ones — there is no channel_has_access check before returning the member list. Any authenticated user who knows a private channel&#39;s UUID can enumerate all users with access to that channel. This vulnerability is fixed in 0.9.0.</p> https://cve.radiocsirt.org/vuln/cve-2026-44559 https://cve.radiocsirt.org/vuln/pysec-2026-2720 <p><strong>Affected:</strong> PyPI: open-webui</p> <p># Missing Access Check on Channel Members Endpoint for Standard Channels</p> <p>## Affected Component</p> <p>Channel members listing endpoint: - `backend/open_webui/routers/channels.py` (lines 445-507, `get_channel_members_by_id`)</p> <p>## Affected Versions</p> <p>Current main branch and likely all versions with the channels feature.</p> <p>## Description</p> <p>The `GET /api/v1/channels/{id}/members` endpoint only checks membership for `group` and `dm` channel types (lines 467-469). For standard channels — including private ones — there is no `channel_has_access` check before returning the member list. Any authenticated user who knows a private channel&#39;s UUID can enumerate all users with access to that channel.</p> <p>```python # Line 467-469: only group/dm channels are checked if channel.type in [&#39;group&#39;, &#39;dm&#39;]: if not Channels.is_user_channel_member(channel.id, user.id, db=db): raise HTTPException(...) # Standard channels fall through with NO access check ```</p> <p>Compare with other channel endpoints (e.g., `get_channel_messages` at line 688) which correctly call `channel_has_access(user.id, channel, permission=&#39;read&#39;)` for standard channels.</p> <p>## CVSS 3.1 Breakdown</p> <p>| Metric | Value | Rationale | |--------|-------|-----------| | Attack Vector | Network (N) | Exploited remotely via API call | | Attack Complexity | Low (L) | Single API call, no special conditions | | Privileges Required | Low (L) | Requires a valid user account | | User Interaction | None (N) | No victim interaction required | | Scope | Un…</p> <p><strong>Affected:</strong> PyPI: open-webui</p> <p># Missing Access Check on Channel Members Endpoint for Standard Channels</p> <p>## Affected Component</p> <p>Channel members listing endpoint: - `backend/open_webui/routers/channels.py` (lines 445-507, `get_channel_members_by_id`)</p> <p>## Affected Versions</p> <p>Current main branch and likely all versions with the channels feature.</p> <p>## Description</p> <p>The `GET /api/v1/channels/{id}/members` endpoint only checks membership for `group` and `dm` channel types (lines 467-469). For standard channels — including private ones — there is no `channel_has_access` check before returning the member list. Any authenticated user who knows a private channel&#39;s UUID can enumerate all users with access to that channel.</p> <p>```python # Line 467-469: only group/dm channels are checked if channel.type in [&#39;group&#39;, &#39;dm&#39;]: if not Channels.is_user_channel_member(channel.id, user.id, db=db): raise HTTPException(...) # Standard channels fall through with NO access check ```</p> <p>Compare with other channel endpoints (e.g., `get_channel_messages` at line 688) which correctly call `channel_has_access(user.id, channel, permission=&#39;read&#39;)` for standard channels.</p> <p>## CVSS 3.1 Breakdown</p> <p>| Metric | Value | Rationale | |--------|-------|-----------| | Attack Vector | Network (N) | Exploited remotely via API call | | Attack Complexity | Low (L) | Single API call, no special conditions | | Privileges Required | Low (L) | Requires a valid user account | | User Interaction | None (N) | No victim interaction required | | Scope | Un…</p> https://cve.radiocsirt.org/vuln/pysec-2026-2720