Skip to content

← Actionable
Medium, CVSS 5.4amended

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

CVE-2026-44561GHSA-hmgr-67hw-j2cq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.9.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-44561: 0.18% estimated exploitation activity in the next 30 days; percentile 7.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Deactivated Channel Members Retain Full Access to Group/DM Channels Affected Component Channel membership authorization check: - backend/openwebui/models/channels.py (lines 663-673, isuserchannelmember) - Used at 15 locations in backend/openwebui/routers/channels.py Affected Versions Current main branch (commit 6fdd19bf1) and likely all versions with the group/DM channel feature. Description The isuserchannelmember function checks whether a ChannelMember row exists but does not check the isactive 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 isactive=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 getchannelsbyuserid properly filters on isactive), but all 15…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-hmgr-67hw-j2cq

  2. Revision 1 · created ·

    Published from osv record GHSA-hmgr-67hw-j2cq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44561

Advisory: Open WebUI: Deactivated Channel Members Retain Full Access to Group/DM Channels
IDs: CVE-2026-44561, GHSA-hmgr-67hw-j2cq
Record: https://patchnext.com/advisories/cve-2026-44561 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: open-webui 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI open-webui: affected <= 0.8.12; fixed in 0.9.0

## Suggested inspection (read-only)
- `python -m pip show open-webui`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on open-webui.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hmgr-67hw-j2cq (OSV record GHSA-hmgr-67hw-j2cq lists affected ranges: PyPI open-webui >=0 <0.9.0 (fixed))
- Verified: https://github.com/advisories/GHSA-hmgr-67hw-j2cq (GitHub-reviewed advisory GHSA-hmgr-67hw-j2cq lists affected ranges: PyPI open-webui >=0 <=0.8.12)

Commands are suggestions: review each one before running it.

Loading voting…