CVE-2026-4636: Keycloak: keycloak: uma policy bypass allows authenticated users to gain unauthorized access to victim-owned resources.
A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA) policy validation. This allows the attacker to include resource identifiers owned by other users in a policy creation request, even if the URL path specifies an attacker-owned resource. Consequently, the attacker gains unauthorized permissions to victim-owned resources, enabling them to obtain a Requesting Party Token (RPT) and access sensitive information or perform unauthorized actions.
Security readout for executives and security teams
Plain-English summary
CVE-2026-4636 is a high-severity Keycloak authorization flaw. A logged-in user with the uma_protection role may bypass UMA policy checks and gain access to resources owned by other users. This could expose sensitive data or allow unauthorized actions in systems relying on affected Red Hat Keycloak builds for access control.
Executive priority
Prioritize remediation for internet-facing or shared Keycloak environments using UMA authorization. This is not marked as actively exploited in the provided sources, but the potential business impact is unauthorized access to protected resources, including sensitive information and privileged actions.
Technical view
The flaw affects UMA policy validation in Red Hat build of Keycloak. An authenticated user with uma_protection can include victim-owned resource identifiers in a policy creation request, despite the request path targeting an attacker-owned resource. Successful abuse can permit RPT issuance for unauthorized resources. CVSS is 8.1, with low attack complexity and high confidentiality and integrity impact.
Likely exposure
Exposure is most likely in deployments using affected Red Hat build of Keycloak 26.2 or 26.4 packages and UMA authorization features. The attacker must already be authenticated and have the uma_protection role. Systems that do not use UMA or do not grant that role broadly have lower practical exposure.
Exploitation context
The source bundle does not cite active exploitation, and KEV status is false. The issue is still serious because exploitation requires only network access, low complexity, no user interaction, and a privileged-but-plausible authenticated role. Evidence for public exploit availability is not provided in the bundle.
Researcher notes
Focus validation on authorization-server resource policy creation and role scoping. Do not assume all Keycloak deployments are affected; the provided affected list is specific to Red Hat build of Keycloak 26.2 and 26.4 packages. The bundle identifies CWE-551, but detailed root-cause code evidence is not included.
Mitigation direction
Review RHSA-2026:6475 through RHSA-2026:6478 for the correct Red Hat update path.
Upgrade affected Red Hat build of Keycloak packages to vendor-fixed releases.
Restrict uma_protection role assignments to trusted accounts until updates are applied.
Audit UMA clients and resources for unexpected policy grants or RPT issuance.
Monitor Red Hat CVE and Bugzilla pages for revised remediation guidance.
Validation and detection
Inventory Keycloak deployments and identify Red Hat build versions 26.2 and 26.4.
Check installed package names against the affected package list in the CVE record.
Confirm whether UMA authorization is enabled for protected resources.
Review accounts granted the uma_protection role.
After patching, verify package versions match Red Hat fixed guidance.
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-551: 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 authentication or credential exposure, so valid-account and credential-access 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.
2CVSS vectors
7Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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-551 · source CWE mapping
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.