Bug 2577541 (CVE-2026-133536) - CVE-2026-133536 org.keycloak:keycloak-services: Post-logout redirect URI configuration of a disabled client is still honored, leading to open redirect
Summary: CVE-2026-133536 org.keycloak:keycloak-services: Post-logout redirect URI conf...
Keywords:
Status: NEW
Alias: CVE-2026-133536
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 02:41 UTC by OSIDB Bzimport
Modified: 2026-11-20 02:42 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 02:41:35 UTC
The OpenID Connect logout endpoint (GET

/realms/{realm}/protocol/openid-connect/logout) still applies a
client's post-logout redirect URI configuration after the client has
been disabled. A disabled client should be rejected with an error, as
the authorization endpoint does, and its redirect allowlist should be
ignored. Instead, if a disabled client was configured with a
permissive post-logout redirect URI (for example "*", or a redirect
URI of "*" with an empty post-logout redirect URI), a request for the
logout endpoint with that client_id and an arbitrary
post_logout_redirect_uri redirects the browser to the attacker-chosen
URL. When the victim has an active session, Keycloak shows the logout
confirmation page first. When the victim has no active session, the
browser is redirected directly, which results in an open redirect.
Disabling a misconfigured client is expected to neutralize the issue,
and it does not. The same behavior was confirmed on a build of main,
where the redirect is also honored after the user confirms the logout.


Note You need to log in before you can comment on or make changes to this bug.