MISFIRE

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

Open WebUI: Deactivated Channel Members Retain Full Access to Group/DM Channels

CVE-2026-44561 · 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)
Gets past
Authorisation check
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

The channel membership check does not look at the active flag, so users removed from a group or DM channel can still read and post via direct API calls. (Our summary, written by a model. The source text is below.)

Details

Deactivated Channel Members Retain Full Access to Group/DM Channels

Affected Component

Channel membership authorization check:
- backend/open_webui/models/channels.py (lines 663-673, is_user_channel_member)
- Used at 15 locations in backend/open_webui/routers/channels.py

Affected Versions

Current main branch (commit 6fdd19bf1) and likely all versions with the group/DM channel feature.

Description

The is_user_channel_member function checks whether a ChannelMember row exists but does not check the is_active field. When a user is deactivated from a group or DM channel (removed by the channel owner, or leaves voluntarily), their membership row persists with is_active=False and status='left'. Because the authorization check ignores this field, the deactivated user retains full read and write access to the channel via direct API calls.

The channel correctly disappears from the deactivated user's channel list (the listing query at get_channels_by_user_id properly filters on is_active), but all 15 message-level endpoints in the router rely on is_user_channel_member for authorization, which does not filter on is_active.

# models/channels.py:663 — missing is_active check
def is_user_channel_member(self, channel_id, user_id, db=None):
    membership = db.query(ChannelMember).filter(
        ChannelMember.channel_id == channel_id,
        ChannelMember.user_id == user_id,
    ).first()
    return membership is not None  # True even when is_active=False

Compare with get_channel_by_id_and_user_id (line 778) which correctly checks ChannelMember.is_active.is_(True).

CVSS 3.1 Breakdown

| Metric | Value | Rationale |
|--------|-------|-----------|
| Attack Vector | Network (N) | Exploited remotely via API calls |
| Attack Complexity | Low (L) | No special conditions beyond knowing the channel ID (which the user had as a former member) |
| Privileges Required | Low (L) | Requires a valid user account and prior channel membership |
| User Interaction | None (N) | No victim interaction required |
| Scope | Unchanged (U) | Impact is within the same authorization boundary (the channel) |
| Confidentiality | Low (L) | Can read messages in a channel the user should no longer access |
| Integrity | Low (L) | Can post, edit, and delete messages in the channel |
| Availability | None (N) | No denial of service |

Attack Scenario

Impact

Preconditions

Recommended Fix

Add is_active filtering to is_user_channel_member:

def is_user_channel_member(self, channel_id, user_id, db=None):
    membership = db.query(ChannelMember).filter(
        ChannelMember.channel_id == channel_id,
        ChannelMember.user_id == user_id,
        ChannelMember.is_active.is_(True),
    ).first()
    return membership is not None

This aligns it with the existing get_channel_by_id_and_user_id method which already applies this filter correctly.

References

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