CVE-2025-14778
A flaw was found in Keycloak. A significant Broken Access Control …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/errata/RHSA-2026:2363
- access.redhat.com/errata/RHSA-2026:2364
- access.redhat.com/errata/RHSA-2026:2365
- access.redhat.com/errata/RHSA-2026:2366
- access.redhat.com/security/cve/CVE-2025-14778
- bugzilla.redhat.com/show_bug.cgi?id=2422600
- nvd.nist.gov/vuln/detail/CVE-2025-14778
- github.com/keycloak/keycloak/issues/46147
- nvd.nist.gov/vuln/detail/CVE-2025-14778
- cve.org/CVERecord?id=CVE-2025-14778
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.