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.
Security readout for executives and security teams
Plain-English summary
An authenticated Keycloak administrator who controls one client could alter or delete authorization resources belonging to another client in the same realm. This could disrupt access controls or services across organizational boundaries, but requires substantial existing privileges and a valid resource identifier.
Executive priority
Schedule prompt remediation where multiple teams or tenants share a realm with delegated client administrators. Prioritize those deployments over realms controlled exclusively by a small, trusted central administration team. No source supports emergency treatment based on active exploitation.
Technical view
Authorization is checked using the request’s resource-server client ID, while database lookup and modification use only the resource ID. This identifier mismatch enables cross-client access within one realm. CVSS 3.1 is 6.0, reflecting network reachability, low complexity, high privileges, and primarily integrity impact.
Likely exposure
Exposure is established for the listed Red Hat build of Keycloak 26.4 packages and versions. Risk is greatest in shared realms using fine-grained delegated client administration. The supplied evidence does not establish impact to other Keycloak distributions or versions.
Exploitation context
The attacker must already be authenticated with fine-grained administrative permissions for a client and possess a valid resource ID from another client in the same realm. The supplied sources provide no evidence of active exploitation, and the CVE is not listed as KEV.
Researcher notes
The bundle lists rhbk/keycloak-operator-bundle 26.4.11-1, rhbk/keycloak-rhel9 26.4-14, and rhbk/keycloak-rhel9-operator 26.4-14 as affected. It separately marks rhbk/keycloak-rhel9-operator under product 26.4.11 as unaffected. Resolve this package-specific distinction through the cited errata before declaring exposure.
Mitigation direction
Review RHSA-2026:6477 and RHSA-2026:6478, then apply the applicable Red Hat updates to affected packages.
Until updated, restrict fine-grained client administration to trusted accounts and limit administrative API access.
Remove unnecessary delegated client permissions and separate administrative trust boundaries where operationally practical.
Validation and detection
Inventory Red Hat Keycloak packages, exact builds, realms, and fine-grained client administration assignments.
Compare each installed package and version with the package-specific status in Red Hat advisories.
Confirm delegated administrators cannot modify or delete another client’s authorization resources in a controlled environment.
Review available administrative audit records for unexpected cross-client resource changes or deletions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-289: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-289 · source CWE mapping
Authentication Bypass by Alternate Name
Authentication Bypass by Alternate Name represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.