Keycloak on Red Hat Group Members Endpoint insufficient granularity of access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.7 | $0-$5k | 0.79 |
Summary
A vulnerability was found in Keycloak on Red Hat. It has been classified as problematic. This vulnerability affects unknown code of the component Group Members Endpoint. Performing a manipulation results in insufficient granularity of access control. This vulnerability is reported as CVE-2026-9088. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Keycloak on Red Hat (unknown version). This affects an unknown code block of the component Group Members Endpoint. The manipulation with an unknown input leads to a insufficient granularity of access control vulnerability. CWE is classifying the issue as CWE-1220. The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. This is going to have an impact on confidentiality. The summary by CVE is:
A flaw was found in org.keycloak.services. An administrator with delegated access to read group memberships and users can bypass user profile permissions by accessing the group members endpoint. This allows the administrator to view user attributes that are explicitly configured to be denied, leading to information disclosure.
The advisory is shared at access.redhat.com. This vulnerability is uniquely identified as CVE-2026-9088 since 05/20/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-34790). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.7VulDB Meta Temp Score: 2.7
VulDB Base Score: 2.7
VulDB Temp Score: 2.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 2.7
CNA Vector (redhat): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Insufficient granularity of access controlCWE: CWE-1220 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/20/2026 CVE reserved06/05/2026 Advisory disclosed
06/05/2026 VulDB entry created
06/05/2026 VulDB entry last update
Sources
Advisory: access.redhat.comStatus: Not defined
CVE: CVE-2026-9088 (🔒)
GCVE (CVE): GCVE-0-2026-9088
GCVE (VulDB): GCVE-100-368877
EUVD: 🔒
Entry
Created: 06/05/2026 10:16Updated: 06/05/2026 12:06
Changes: 06/05/2026 10:16 (60), 06/05/2026 12:06 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.