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
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2.13-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2-15 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2-15 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2.13
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4.9-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-11 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-10 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4.9
Default version status: unaffected
References
- https://access.redhat.com/errata/RHSA-2026:2363 ↗
- https://access.redhat.com/errata/RHSA-2026:2364 ↗
- https://access.redhat.com/errata/RHSA-2026:2365 ↗
- https://access.redhat.com/errata/RHSA-2026:2366 ↗
- https://access.redhat.com/security/cve/CVE-2025-14778 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2422600 ↗