Bug 2577541 (CVE-2026-133536)
| Summary: | CVE-2026-133536 org.keycloak:keycloak-services: Post-logout redirect URI configuration of a disabled client is still honored, leading to open redirect | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | aschwart, aszczucz, boliveir, drichtar, mposolda, pjindal, rmartinc, ssilvert, sthorger, vmuzikar |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in Keycloak. The OpenID Connect (OIDC) logout endpoint continues to honor post-logout redirect rules for disabled clients rather than rejecting the requests. If a disabled client retains permissive redirect configurations, a remote attacker can exploit this issue by supplying an arbitrary redirection target in a logout request, leading to an open redirect that can be used in phishing attacks.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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.