JWT Authentication Bypass in Open WebUI

Compliance Impact

This vulnerability allows revoked JWTs to continue authenticating realtime connections, potentially enabling unauthorized access to sensitive realtime data and user interactions.

Such unauthorized access to sensitive data could lead to violations of data protection regulations like GDPR and HIPAA, which require strict control over access to personal and sensitive information.

By allowing revoked tokens to bypass revocation checks in realtime endpoints, the system risks non-compliance with standards that mandate effective session termination and access revocation mechanisms.

Useful 0 Not Useful 0

Executive Summary

CVE-2026-59219 is a vulnerability in Open WebUI versions 0.9.0 to 0.9.9 when Redis is configured. The realtime endpoints, such as Socket.IO and terminal WebSocket connections, authenticate users using JWT tokens but fail to check if these tokens have been revoked. While HTTP authentication correctly rejects revoked tokens, the realtime authentication only verifies token signatures and expiry, allowing revoked tokens to still establish realtime connections.

This means that users who have signed out or had their tokens revoked can still access realtime features, potentially impersonating the victim user or accessing sensitive realtime data.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can allow an attacker with a revoked JWT token to continue authenticating realtime connections in Open WebUI. As a result, the attacker could access sensitive realtime data, collaborate as the victim user, or interact with terminal sessions without proper authorization.

The impact includes unauthorized access to confidential information and potential misuse of user privileges in realtime communication channels.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves realtime endpoints accepting revoked JWT tokens without proper revocation checks. Detection involves monitoring realtime Socket.IO and terminal WebSocket connections for authentication attempts using revoked tokens.

You can detect exploitation attempts by inspecting realtime connection logs for JWT tokens that should have been revoked but are still accepted. Since the issue is related to token revocation checks missing in realtime authentication, commands or scripts that query Redis for revoked tokens and cross-reference active realtime connections could help.

• Use Redis CLI commands to check revoked tokens, for example: `redis-cli KEYS revoked_tokens*` or querying token JTIs stored in Redis.
• Monitor WebSocket connection logs or Socket.IO events to identify connections authenticated with tokens that should be revoked.
• Implement or use scripts that decode JWT tokens from realtime connections and verify their revocation status against Redis.

Useful 0 Not Useful 0

Mitigation Strategies

The primary mitigation is to upgrade Open WebUI to version 0.10.0 or later, where the vulnerability is fixed by adding proper token revocation checks to realtime endpoints.

Until you can upgrade, consider disabling realtime features that rely on Socket.IO and terminal WebSocket connections if feasible, to prevent use of revoked tokens in realtime authentication.

Ensure that Redis is properly configured and accessible for token revocation checks, as the fix depends on validating tokens against Redis.

Review and monitor authentication logs for suspicious realtime connections using revoked tokens and revoke any suspicious sessions manually if possible.

Useful 0 Not Useful 0