REDHAT-BUG-2577141: Medium severity Keycloak Keycloak vulnerability

Published Nov 19, 2026
·
Updated

After an administrator disables a client that has Authorization

Services enabled (a resource server), Keycloak still issues new Requesting Party Tokens (RPTs) that target that disabled client. The UMA grant resolves the target resource server by checking only that the client and its authorization settings exist, and never checks whether the client is enabled. Keycloak then adds the disabled client to the RPT audience and includes the user's granted permissions. This bypasses the administrator's action of disabling the client, because ordinary token issuance excludes disabled clients from the audience of new tokens. The resulting RPT remains usable by any resource server or policy enforcement point that validates the signature, audience and embedded authorization data locally. The affected endpoint is the token endpoint (POST /realms/{realm}/protocol/openid-connect/token) using the UMA grant (urn:ietf:params:oauth:grant-type:uma-ticket).

Affected Software

1 affected component
Keycloak Keycloak

Frequently Asked Questions

1

Which deployments are exposed to practical impact?

Deployments are exposed when a disabled client has Authorization Services enabled and a resource server or policy enforcement point accepts RPTs through local validation of their signature, audience, and embedded authorization data.

2

What request path is involved in obtaining an affected token?

The issue is triggered through the realm token endpoint using the UMA ticket grant. The request is sent to POST /realms/{realm}/protocol/openid-connect/token with grant type urn:ietf:params:oauth:grant-type:uma-ticket.

3

Does disabling the client prevent newly issued RPTs from naming it as an audience?

No. UMA grant processing can still resolve the disabled client, add it to the RPT audience, and include the user's granted permissions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203