keycloak-services is vulnerable to Authentication Bypass
81
CVE Score
High
Authentication Bypass
Keycloak provides a Dynamic Client Registration feature that allows users with specific tokens to register their own applications. A flaw in how Keycloak validates these registration requests allows an attacker to create a malicious application that forges identity information. By mapping their own user profile details to protected fields like the user ID (sub) or intended audience (aud), an attacker can generate signed security tokens that make them appear to be a different user. This could allow an attacker to impersonate other users or gain unauthorized access to services that rely on these tokens for identity verification.
Upgrade org.keycloak:keycloak-services to the patched version. The fix restricts mapper changes and enforces a realm-administrator-controlled allowlist for registration mapper types.
You are affected if you use a vulnerable version of org.keycloak:keycloak-services and holders of Initial Access Tokens can register clients with protocol mappers that map user data to protected identity claims.
2.3.0.Final - 26.4.16
Fixed in 26.4.1726.5.0 - 26.6.7
Fixed in 26.6.826.7.0 - 26.8.1
Fixed in 26.8.2keycloak-services is vulnerable to Authentication Bypass in versions 2.3.0.Final - 26.4.16, 26.5.0 - 26.6.7 and 26.7.0 - 26.8.1.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.