MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2026-44559

Open WebUI Missing Access Check on Channel Members Endpoint for Standard Channels

CVE-2026-44559 · 2026-05-08 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the source)
Technique
Authentication and access control
Affected
open-webui (PyPI)
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

The channel member listing skips the access check for standard channels, letting any logged-in user enumerate members of a private channel given its ID. (Our summary, written by a model. The source text is below.)

Details

Missing Access Check on Channel Members Endpoint for Standard Channels

Affected Component

Channel members listing endpoint:
- backend/open_webui/routers/channels.py (lines 445-507, get_channel_members_by_id)

Affected Versions

Current main branch and likely all versions with the channels feature.

Description

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's UUID can enumerate all users with access to that channel.

# Line 467-469: only group/dm channels are checked
if channel.type in ['group', 'dm']:
    if not Channels.is_user_channel_member(channel.id, user.id, db=db):
        raise HTTPException(...)
# Standard channels fall through with NO access check

Compare with other channel endpoints (e.g., get_channel_messages at line 688) which correctly call channel_has_access(user.id, channel, permission='read') for standard channels.

CVSS 3.1 Breakdown

| 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 | Unchanged (U) | Impact is within the channel authorization boundary |
| Confidentiality | Low (L) | Leaks user identities and details for a private channel |
| Integrity | None (N) | No data modification |
| Availability | None (N) | No denial of service |

Attack Scenario

Impact

Preconditions

References

Source: GitHub Advisory Database, used under CC BY 4.0.