Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain restricted admin credentials
-
DeliveryAuthenticate to Keycloak admin REST API
-
ExploitQuery role-to-group membership endpoint
-
ExecutionBypass group-view authorization check
-
PersistEnumerate hidden group names and attributes
-
ImpactUse topology data for reconnaissance or follow-on attacks
Vulnerability Assessment
| Weakness |
CWE
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | FGAP v2 (Fine-Grained Admin Permissions version 2) must be explicitly enabled in the Keycloak realm - this is a non-default, opt-in feature. The attacker must hold a valid, authenticated Keycloak administrator account with at least role-view permission granted under the FGAP v2 model. Exploitation is not possible against standard Keycloak deployments where FGAP v2 is disabled, nor against environments where all admin accounts hold full (non-restricted) administrative scope. The CVSS PR:L metric confirms authentication as a restricted admin is required; unauthenticated exploitation is not possible. Exploitation is limited to read-only group metadata disclosure - no write, delete, or privilege escalation capability is exposed through this flaw. The impacted information is group names and custom attributes, which may or may not carry operationally sensitive content depending on how the organization uses group attributes. |
| Impact | The CVSS 3.1 base score of 4.3 (Medium) reflects a network-accessible, low-privilege, no-interaction flaw with limited confidentiality impact and no integrity or availability exposure - an accurate characterization for an information-disclosure-only finding. The S:U (Unchanged scope) metric confirms no lateral privilege escalation is possible through this bug alone; it is a reconnaissance aid, not an exploitation primitive. No EPSS data was provided, and the vulnerability is absent from CISA KEV, indicating no confirmed active exploitation. The real-world risk is further constrained by the requirement for FGAP v2 to be explicitly enabled - a non-default, opt-in feature not present in standard Keycloak deployments. The primary threat model is insider or delegated-admin abuse: an attacker who already holds a restricted admin credential could map hidden group topology and harvest group attribute data (e.g., environment names, integration endpoints, tenant tags). That reconnaissance value may enable privilege escalation through social engineering or inform follow-on attacks, but the vulnerability does not itself grant access beyond metadata. No CVSS or exploitation signal conflicts exist in the available data. |
| Exploit ScenarioDerived | An attacker who has obtained a restricted Keycloak administrator credential - one scoped only to role-view permissions within FGAP v2 - sends a query to the Keycloak admin REST API requesting the group membership list for a role they are authorized to view. The response returns all groups assigned to that role without a secondary group-view authorization check, exposing group names, descriptions, and custom attributes. The attacker uses this information to map the hidden group topology of the realm, potentially discovering environment-specific group names, integration identifiers, or deployment annotations stored as group attributes that were intended to be invisible to restricted admins. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 03, 2026
Keycloak's Fine-Grained Admin Permissions v2 (FGAP v2) fails to enforce group-level authorization when a restricted administrator queries role-to-group assignments, exposing group names and custom attributes beyond the admin's intended scope. Restricted admins holding only role-view permission can enumerate all groups assigned to that role, bypassing the group-level access controls that FGAP v2 is designed to enforce. No public exploit code exists and this vulnerability has not been added to the CISA KEV catalog; however, the EPSS risk is compounded in deployments where group attributes carry sensitive operational metadata.
RemediationAI
The primary remediation is to apply the patch released by Red Hat, available via the Red Hat Security Advisory at https://access.redhat.com/security/cve/CVE-2026-14613. No exact fixed version number was included in the available input data; security teams should consult the advisory directly to identify the target package version for their specific product (Red Hat Build of Keycloak, RH-SSO 7, Data Grid 8, or JBoss EAP Expansion Pack). As an interim compensating control prior to patching, organizations should disable FGAP v2 if it is not actively required, which eliminates the vulnerable code path entirely at the cost of reverting to coarser-grained admin delegation. If FGAP v2 cannot be disabled, audit all delegated admin accounts to ensure that only trusted administrators hold role-view permissions, and review group attributes to ensure that sensitive deployment metadata is not stored directly in Keycloak group properties. The trade-off of disabling FGAP v2 is loss of granular delegation capability, which may affect multi-tenant or MSP-style deployments. No patch version is independently confirmed from the available input data.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Keycloak is Red Hat's enterprise identity and access management platform, providing single sign-on and federated identity services across Red Hat Single Sign-On 7, Red Hat Build of Keycloak, Red Hat JBoss EAP Expansion Pack, and Red Hat Data Grid 8. FGAP v2 is a feature designed to enforce granular delegation - allowing tenant administrators to manage only specific realms, roles, or groups rather than the entire Keycloak instance. The vulnerability is a missing authorization check in the code path that resolves group membership for a given role. While CWE is unassigned by the reporter, the root cause class is Improper Authorization (CWE-285): the system correctly validates that the caller can view the role, but omits a secondary check to confirm the caller holds group-view permission for each group returned in that role's member list. This is an authorization logic gap in the FGAP v2 permission intersection model, not a bypass of the authentication layer itself.
Know when Red Hat Build Of Keycloak gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Network-accessible admin API requires authenticated low-privilege admin; only group metadata disclosed, no integrity or availability impact.
Primary rating from Vendor (redhat).
CVSS VectorNVD
Lifecycle Timeline
1DescriptionNVD
A vulnerability was discovered in Keycloak's administrative interface that allows certain administrators to see information about groups they shouldn't have access to. When the new Fine-Grained Admin Permissions (FGAP v2) are turned on, an administrator who is allowed to see a specific "role" can also see a list of all groups assigned to that role. The system fails to check if the administrator has permission to see those specific groups. This could allow a restricted administrator to discover "hidden" groups and see their details, such as internal names and custom settings, which might contain sensitive deployment information.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)NVD
More in Red Hat Build Of Keycloak
View allAccount takeover in Red Hat Build of Keycloak allows an unauthenticated attacker to abuse the reset-credentials flow in
Account takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML
Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge
Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privil
Mismatched handling of the HTTP/1 absolute-form request authority in Red Hat build of Quarkus and other affected Red Hat
Authorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con
URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to re
Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accou
Token exchange in Keycloak bypasses Google Workspace domain allowlist restrictions, enabling any valid Google account ho
Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re
Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Micro
Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to aut
EUVD-2026-41555
GHSA-j2vp-w8g9-p6hf
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB