CVE-2026-59219 Open WebUI: Realtime endpoints accept Redis-revoked JWTs after signout/backchannel logout

High 7.1 Published Updated

Attackers can maintain unauthorized realtime access using revoked JWTs if Redis is configured, bypassing logout mechanisms in Open WebUI.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-59219?

CVE-2026-59219 is a high-severity authentication bypass vulnerability in Openwebui Open Webui, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.0 before 0.10.0 with Redis configured, Socket.IO connect, user-join, join-channels, join-note, and the terminal websocket first-message authentication used decode_token without the Redis-backed is_valid_token revocation check, allowing revoked JWTs to continue authenticating realtime connections. This issue is fixed in version 0.10.0.

Weakness: CWE-613

Which versions are affected by CVE-2026-59219?

3 open source packages ship an affected version, including open-webui. It affects 1 product.

PackageAffectedFixed in
open-webui PyPIFrom 0.9.00.10.0
open-webui PyPIFrom 0.9.00.10.0
open-webui PyPIFrom 0.9.00.10.0

Products include Openwebui Open Webui.

How do I fix CVE-2026-59219?

Upgrade open-webui to 0.10.0 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-59219 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59219 exists.

All Openwebui Open Webui vulnerabilities

Sources

Also known as GHSA-855v-hq7w-jmjw, PYSEC-2026-3595.

Is CVE-2026-59219 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free