CVE-2025-14778: Keycloak: incorrect ownership checks in /uma-policy/

Severity: medium (CVSS 5.4 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-02-09 · updated 2026-06-17
Weakness: CWE-266

Description

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.

Affected products

Red Hat build of Keycloak 26.4: all versions — fixed in 26.2-15, 26.2.13-1, 26.4-10, 26.4-11, 26.4.9-1

How to fix

Upgrade to a fixed version: Red Hat build of Keycloak 26.4 26.2-15, 26.2.13-1, 26.4-10, 26.4-11. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-14778 or the next vulnerability affects your stack