CVE-2026-4636: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization in Red Hat Red Hat build of Keycloak 26.2
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.
AI Analysis
Technical Summary
The vulnerability in Red Hat build of Keycloak 26.2 prior to 26.2.15 involves incorrect ordering of authorization checks before parsing and canonicalization in UMA policy validation. Authenticated users with the uma_protection role can bypass policy validation by including resource identifiers owned by other users in policy creation requests. This bypass allows attackers to gain unauthorized permissions to victim-owned resources and obtain Requesting Party Tokens (RPT), leading to unauthorized access to sensitive information or actions. The issue is tracked as CVE-2026-4636 with a CVSS 3.1 score of 8.1 (High). Red Hat has published security advisories and released version 26.2.15 to fix this vulnerability.
Potential Impact
An attacker with authenticated access and the uma_protection role can bypass UMA policy validation to gain unauthorized access to resources owned by other users. This can lead to unauthorized disclosure of sensitive information or unauthorized actions performed on victim-owned resources. The vulnerability affects confidentiality and integrity but does not impact availability.
Mitigation Recommendations
Red Hat has released an official fix in Red Hat build of Keycloak version 26.2.15. Users should upgrade to version 26.2.15 or later to remediate this vulnerability. Before applying the update, back up existing installations, including applications, configuration files, and databases. No other mitigations are specified by the vendor.
CVE-2026-4636: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization in Red Hat Red Hat build of Keycloak 26.2
Description
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.
CVSS v3.1
Score 8.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Red Hat build of Keycloak 26.2 prior to 26.2.15 involves incorrect ordering of authorization checks before parsing and canonicalization in UMA policy validation. Authenticated users with the uma_protection role can bypass policy validation by including resource identifiers owned by other users in policy creation requests. This bypass allows attackers to gain unauthorized permissions to victim-owned resources and obtain Requesting Party Tokens (RPT), leading to unauthorized access to sensitive information or actions. The issue is tracked as CVE-2026-4636 with a CVSS 3.1 score of 8.1 (High). Red Hat has published security advisories and released version 26.2.15 to fix this vulnerability.
Potential Impact
An attacker with authenticated access and the uma_protection role can bypass UMA policy validation to gain unauthorized access to resources owned by other users. This can lead to unauthorized disclosure of sensitive information or unauthorized actions performed on victim-owned resources. The vulnerability affects confidentiality and integrity but does not impact availability.
Mitigation Recommendations
Red Hat has released an official fix in Red Hat build of Keycloak version 26.2.15. Users should upgrade to version 26.2.15 or later to remediate this vulnerability. Before applying the update, back up existing installations, including applications, configuration files, and databases. No other mitigations are specified by the vendor.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-03-23T08:51:40.787Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/errata/RHSA-2026:6475","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:6476","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:6477","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:6478","vendor":"Red Hat"},{"url":"https://access.redhat.com/security/cve/CVE-2026-4636","vendor":"Red Hat"}]
Threat ID: 69ce6a44e6bfc5ba1dd993b3
Added to database: 04/02/2026, 13:08:20 UTC
Last enriched: 07/15/2026, 09:26:31 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 178
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.