CVE-2026-18203 Details
Description
A flaw was found in the group policy evaluation logic of Keycloak, an identity and access management solution. When a group policy is set to extend permissions to child groups, the system incorrectly uses a simple text-based prefix check to verify group membership. This allows a user who belongs to a different group with a similar starting name to bypass security checks and gain unauthorized access to administrative functions or protected resources.
A vulnerability exists in Keycloak's group policy evaluation logic. When a group policy is set to extend permissions to child groups, the system improperly uses a simple text-based prefix check for verifying group membership. This flaw enables a user in a different group with a similar name prefix to bypass security checks and gain unauthorized access to administrative functions or protected resources. The issue arises in the 'org.keycloak.authorization' component, specifically when the 'extendChildren' option is enabled, allowing access to be incorrectly granted based on prefix collisions in group paths.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 31, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-863 | Incorrect Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| redhat build of keycloak | All versions |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 6, 2026 | CVE Modified | [email protected] |
| Nov 6, 2026 | CVE Modified | [email protected] |
| Aug 7, 2026 | Initial Analysis | [email protected] |
| Aug 1, 2026 | CVE Modified | CISA-ADP |
| Jul 31, 2026 | New CVE Received | [email protected] |