Bug 2577141 (CVE-2026-133225)

Summary: CVE-2026-133225 org.keycloak:keycloak-services: UMA issues fresh RPTs for disabled resource-server clients
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aschwart, aszczucz, boliveir, drichtar, mposolda, pjindal, rmartinc, ssilvert, sthorger, vmuzikar
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Keycloak. When processing token requests using the User-Managed Access (UMA) grant, Keycloak fails to verify whether a target client or resource server is enabled before issuing an authorization token. An authenticated remote user can exploit this flaw to obtain valid Requesting Party Tokens (RPTs) for disabled clients, bypassing administrative access controls and permissions restrictions.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-19 17:59:59 UTC
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).