INCIDENT MAP

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

Open WebUI: Scheduled automations continue after pending-user deactivation and stored model ACL revocation

CVE-2026-59226 ยท 2026-07-24 low

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Also involves
Tool and Agent Misuse
Affected
open-webui (PyPI)
Gets past
Authorisation check
CVSS
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS
0.5% chance of exploitation in 30 days

How it works, in short

Scheduled automations keep running for deactivated pending accounts because the scheduler skips owner status checks and model access logic mishandles that role. (Our summary, written by a model. The source text is below.)

Details

Title: Scheduled automations continue after pending-user deactivation and stored model ACL revocation

Summary

Open WebUI documents pending as a zero-access role used for new sign-ups and deactivated users, and normal HTTP routes enforce that with get_verified_user() (which rejects pending), while automation create/update/run routes additionally require the features.automations permission. Two paths missed that lifecycle gate, so a deactivated (pending) account could keep acting through the background automation scheduler:

Net effect: a deactivated account could continue scheduled chat generation through the background worker, consuming the operator's configured model-provider credentials and reaching a stored automation model ID that its current role/ACL state would no longer permit through normal routes.

Impact

A pending/deactivated account continues to execute due scheduled automations after its access has been revoked, consuming the operator's provider credentials, quota and shared capacity, and bypassing the private-model ACL for the automation's stored model ID. Exploitation requires a previously created active automation and a later transition to pending (deactivation or approval rollback), so it is bounded and not interactive. It does not grant unauthenticated access, account takeover, code execution, or cross-user data exfiltration.

Patched

In 0.10.0:

Credits

@rexpository

References

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