CVE-2026-4636: Keycloak UMA Policy Resource Injection Authorization Bypass
- Vendor
- Red Hat
CVE-2026-4636 is an authorization flaw in Keycloak's User-Managed Access (UMA) handling. An authenticated user holding the uma_protection role can bypass UMA policy validation during policy creation by submitting resource identifiers that belong to other users, even when the request URL path references a resource owned by the attacker. This mismatch between the path-scoped resource context and the resource identifiers accepted in the policy creation request allows cross-user permission grants. As a result, the attacker can create effective permissions over victim-owned resources, obtain a Requesting Party Token (RPT) for those resources, and use that token to access protected data or invoke unauthorized operations.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation results in unauthorized access control changes affecting victim-owned UMA resources. An attacker can grant themselves permissions to resources they do not own, obtain an RPT reflecting those unauthorized permissions, and then access sensitive information or perform unauthorized actions against the victim's protected resources. Based on the available scoring, the vulnerability has high confidentiality and high integrity impact, with no direct availability impact described.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by tightly restricting assignment of the uma_protection role to only trusted principals, reviewing UMA policy creation capabilities, and monitoring for anomalous policy creation or permission grants involving resources not owned by the requesting user. Additional compensating controls may include limiting access to UMA protection APIs and auditing issued RPTs and authorization changes for cross-user resource relationships. Specific vendor-supported mitigations beyond patching are not currently available in the provided information.
Remediation
Patch, then assume compromise.
Upgrade Keycloak to a fixed release that addresses CVE-2026-4636. Available vendor remediation includes the Red Hat build of Keycloak 26.4.11 images and the corresponding 26.4.11 Operator update for OpenShift Container Platform. Apply the relevant product update through normal change-control procedures and back up installations, applications, configuration, and databases before deployment where operationally required.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-4636 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-4636 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-4636?
- Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-4636.
- Is there a patch for CVE-2026-4636?
- Upgrade Keycloak to a fixed release that addresses CVE-2026-4636. Available vendor remediation includes the Red Hat build of Keycloak 26.4.11 images and the corresponding 26.4.11 Operator update for OpenShift Container Platform.
- What products are affected by CVE-2026-4636?
- Red Hat Build Of Keycloak.
- How severe is CVE-2026-4636?
- CVE-2026-4636 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.44% (38th percentile) as of Sep 25, 2026.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.