CVE-2026-133536

Description

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.

Statement

This vulnerability is rated as Moderate severity because exploitation is limited to open redirection and requires a specific prerequisite: an inactive client within the realm must already be configured with overly broad or wildcard post-logout redirect rules. In standard Red Hat build of Keycloak and Red Hat Single Sign-On deployments, disabled clients are expected to reject all protocol interactions; however, their post-logout redirection allowlists remain active at the logout endpoint. While this flaw cannot be leveraged for direct privilege escalation or data exfiltration on the authentication server itself, attackers could use the unvalidated redirect as part of phishing campaigns.

Mitigation

Administrators can mitigate this flaw by removing permissive redirect configurations from inactive clients or deleting unused clients:

1. In the Keycloak Admin Console, navigate to the relevant realm and inspect the 'Clients' list.
2. For any client set to disabled, open its settings and clear or restrict the 'Valid Post Logout Redirect URIs' and 'Valid Redirect URIs' fields, ensuring wildcard characters ('*') are removed and only explicitly trusted absolute URLs remain.
3. Alternatively, permanently delete any disabled clients that are obsolete and no longer required.

Caveats: Deleting a client permanently removes its configuration, mappers, service account roles, and credentials. Changes made to client settings in the Admin Console apply immediately to the realm without requiring a Keycloak service restart.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.3N/A4.3
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactLowN/ALow
Availability ImpactNoneN/ANone

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Understanding the Weakness (CWE)

Access Control

Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity

The user may be redirected to an untrusted page that contains malware which may then compromise the user's system. In some cases, an open redirect can also enable the immediate download of a file without the user's permission, because the redirection to an external site may lead to endpoints on those sites that automatically trigger a download action ("drive-by download" [REF-1478]). This will expose the user to extensive risk. The user's interaction with the web server may also be compromised if the malware conducts keylogging or other attacks that steal credentials, personally identifiable information (PII), or other important data.

Access Control,Confidentiality,Other

Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity; Other

By modifying the URL value to a malicious site, an attacker may successfully launch a phishing scam. The user may be subjected to phishing attacks by being redirected to an untrusted page. The phishing attack may point to an attacker controlled web page that appears to be a trusted web site. The phishers may then steal the user's credentials and then use these credentials to access the legitimate web site. Because the server name in the modified link is identical to the original site, phishing attempts can appear more trustworthy.

Acknowledgements

Red Hat would like to thank Max Maass (iteratec) for reporting this issue.

Frequently Asked Questions

Want to get errata notifications? Sign up here.