REDHAT-BUG-2501729: Medium severity Keycloak keycloak-services vulnerability
A flaw was found in the Secure Client Registration executor within the keycloak-services component. The vulnerability exists in the logic that enforces the signed-JWT assertion policy for client registration and updates. When the SecureSigningAlgorithmForSignedJwtExecutor is configured to require a client assertion, it only checks the alg field in the raw client assertion JWT header. It fails to validate that the client assertion type is present or that the client's actual authenticator is assertion-based. By providing a specially crafted request with an unsigned assertion header containing a valid alg field, an attacker with valid client credentials can bypass the signature verification check. This allows the attacker to successfully authenticate or update a client without providing the required cryptographic proof of identity. Successful exploitation allows an attacker to circumvent administrative security policies intended to restrict client authentication to trusted assertion-based methods.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2501729?
The severity of REDHAT-BUG-2501729 is classified as medium, with a score of 4.
What component of Keycloak is affected by REDHAT-BUG-2501729?
The vulnerability REDHAT-BUG-2501729 affects the keycloak-services component of Keycloak.
What type of flaw does REDHAT-BUG-2501729 describe?
REDHAT-BUG-2501729 describes a flaw in the logic enforcing the signed-JWT assertion policy for client registration and updates.
How can I mitigate REDHAT-BUG-2501729?
Mitigation for REDHAT-BUG-2501729 involves reviewing and potentially reconfiguring the SecureSigningAlgorithmForSignedJwtExecutor settings in Keycloak.
When was REDHAT-BUG-2501729 published?
REDHAT-BUG-2501729 was published on July 17, 2026.