Vendredi 17 juillet 2026

Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.7 · Red Hat Data Grid 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack

A flaw was found in the default-groups REST endpoint and realm representation of Keycloak. This component is responsible for managing groups that are automatically assigned to new users within a realm. The issue allows a delegated administrator with realm-viewing permissions to see the names and identifiers of hidden default groups, even if they lack the specific permissions to view those groups. This can lead to the exposure of sensitive organizational structures or internal group names.

Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.7 · Red Hat Data Grid 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack

A flaw was found in the admin REST API of Keycloak, a solution for identity and access management. The issue occurs when a delegated administrator attempts to remove a child role from a composite role. Due to missing authorization checks, an attacker with limited administrative permissions can remove privileged roles they are not authorized to manage, leading to a loss of access for other users and administrators.

Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.7 · Red Hat Data Grid 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack

A flaw was found in the authentication configuration endpoint of the keycloak-services component, which is the core engine for Red Hat Build of Keycloak identity and access management. The issue occurs because the system fails to mask sensitive configuration values, such as reCAPTCHA secret keys, when they are requested by administrators with view-only permissions. This can lead to the exposure of third-party service credentials to unauthorized personnel or through administrative logs.

Red Hat Build of Keycloak · Red Hat Data Grid 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack · Red Hat Single Sign-On 7

A flaw was found in the keycloak-services component of Keycloak. This issue is an incomplete fix for CVE-2026-9798, where brute-force protection checks were added to the Client-Initiated Backchannel Authentication (CIBA) initiation handler but were omitted from the token redemption handler. This allows an attacker with valid client credentials to obtain access and refresh tokens for a user account that has been locked due to brute-force protection, provided the authentication request was started before the lockout occurred and was approved by the user.

Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.7 · Red Hat Data Grid 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack

Keycloak provides a mechanism called Client Policies to enforce security requirements on clients, such as requiring them to use signed JWTs for authentication. A flaw was discovered where this enforcement can be bypassed. An attacker with valid client credentials can provide a fake, unsigned assertion header that tricks the system into thinking the policy requirements have been met. This allows the attacker to authenticate using simpler methods like a client secret even when the administrator has mandated more secure, signed assertions.

Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.7 · Red Hat Data Grid 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack

A flaw was found in the keycloak-services component of Red Hat Build of Keycloak. The issue occurs because OAuth 2.0 authorization codes are not properly bound to the client that originally requested them. An attacker who can intercept an authorization code can modify it to be redeemed by their own client, potentially allowing them to obtain access tokens for a victim's identity.

Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.7 · Red Hat Data Grid 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack

A flaw was found in the organization management component of Keycloak. A delegated administrator with permission to manage organizations can create an invitation for a non-existent email address and then retrieve the secret registration link directly through the application programming interface. By using this link, the administrator can create new user accounts and add them to the organization without having the required user management permissions or access to the invited email account. This allows an administrator to bypass security boundaries and add unauthorized members to an organization.

Red Hat Build of Keycloak · Red Hat Data Grid 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack · Red Hat Single Sign-On 7

A flaw was found in the Keycloak keycloak-services component, which handles the management of identity providers. The issue occurs when a delegated administrator updates an OIDC identity provider using a masked client secret sentinel value. Due to improper validation, Keycloak reuses the existing real secret even if security-sensitive fields like the token URL have been changed, allowing an attacker to redirect and capture the secret.