Red Hat Keycloak UserManagedPermissionService privileges assignment

Summaryinfo

A vulnerability was found in Red Hat Keycloak. It has been classified as critical. The affected element is an unknown function of the component UserManagedPermissionService. Performing a manipulation results in privileges assignment. This vulnerability is identified as CVE-2025-14778. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Red Hat Keycloak (unknown version). It has been classified as critical. This affects an unknown code block of the component UserManagedPermissionService. The manipulation with an unknown input leads to a privileges assignment vulnerability. CWE is classifying the issue as CWE-266. A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A flaw was found in Keycloak. A significant Broken Access Control vulnerability exists in the UserManagedPermissionService (UMA Protection API). When updating or deleting a UMA policy associated with multiple resources, the authorization check only verifies the caller's ownership against the first resource in the policy's list. This allows a user (Owner A) who owns one resource (RA) to update a shared policy and modify authorization rules for other resources (e.g., RB) in that same policy, even if those other resources are owned by a different user (Owner B). This constitutes a horizontal privilege escalation.

The advisory is shared at access.redhat.com. This vulnerability is uniquely identified as CVE-2025-14778 since 12/16/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/11/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0356). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Open Source Keycloak

Productinfo

Vendor

• Red Hat

Name

• Keycloak

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion