CVE-2025-14777: Keycloak: keycloak idor in realm client creating/deleting
A flaw was found in Keycloak. An IDOR (Broken Access Control) vulnerability exists in the admin API endpoints for authorization resource management, specifically in ResourceSetService and PermissionTicketService. The system checks authorization against the resourceServer (client) ID provided in the API request, but the backend database lookup and modification operations (findById, delete) only use the resourceId. This mismatch allows an authenticated attacker with fine-grained admin permissions for one client (e.g., Client A) to delete or update resources belonging to another client (Client B) within the same realm by supplying a valid resource ID.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-14777?
CVE-2025-14777 has a medium severity rating due to its impact on access control in admin API endpoints.
How do I fix CVE-2025-14777?
To fix CVE-2025-14777, update your Red Hat Keycloak software to the latest patched version provided by Red Hat.
What components are affected by CVE-2025-14777?
CVE-2025-14777 impacts the ResourceSetService and PermissionTicketService components in the Keycloak admin API.
What types of attacks can CVE-2025-14777 enable?
CVE-2025-14777 can enable unauthorized access to resources due to broken access control in the authorization management.
Who is affected by CVE-2025-14777?
Organizations using Red Hat Keycloak for authorization management are affected by CVE-2025-14777.