REDHAT-BUG-2537313: Medium severity Keycloak Keycloak authorization token endpoint vulnerability

Published Sep 21, 2026
·
Updated

A flaw was found in the Keycloak authorization token endpoint. The vulnerability is a logic error in how UMA permission tickets are processed when multiple resources share the same name across different owners. When a requester submits a permission ticket, the endpoint performs a lookup based on the resource name and the requester identity. However, it fails to properly isolate resources by their specific owner, leading to a scope merge where permissions from all matching resource names are aggregated into a single Requesting Party Token (RPT). An authenticated attacker with low privileges can exploit this by creating a resource with the same name as a victim's resource and sharing it with themselves. This triggers the merge mechanism, allowing the attacker to obtain an RPT containing scopes belonging to the victim's resource. This bypasses the standard policy engine evaluation for the victim's resource. Successful exploitation requires that the victim has previously shared their resource.

Affected Software

1 affected component
Keycloak Keycloak authorization token endpoint

Event History

Sep 21, 2026
Data Sourced
via Red Hat·06:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Keycloak deployments using the authorization token endpoint are exposed when a victim has previously shared a resource. The issue requires multiple resources with the same name under different owners.

2

What does an attacker need to exploit it?

The attacker must be authenticated, even with low privileges. They need to create a resource using the same name as the victim's resource, share that resource with themselves, and submit a permission ticket.

3

Does exploitation require the victim resource to be publicly accessible?

No. The stated prerequisite is that the victim previously shared the resource; the flaw can then cause scopes from that resource to be included in the attacker's Requesting Party Token.

4

What is the security impact of a successful exploit?

The attacker can receive an RPT containing scopes belonging to the victim's resource. This bypasses normal policy-engine evaluation for the victim resource.

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