Recherche « Redhat data grid »

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

A flaw was found in the user-event metrics recording of Keycloak. When metrics are enabled, the system records raw error messages from failed account operations as Prometheus metric labels. Because these error messages can include user-supplied input like nonexistent client IDs, an authenticated user can create a massive number of unique metric entries, eventually exhausting system memory and causing the service to crash or become unavailable.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.14 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.5

A flaw was found in the LDAP storage provider of Keycloak, which is used to federate user identities from external directories. The issue occurs when a delegated administrator performs a search using a specific LDAP entry Distinguished Name (DN). Due to missing validation, the system allows lookups for users located outside the configured search boundary, leading to the disclosure of account information from unauthorized parts of the directory and unintended importing of those users into local storage.

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 Keycloak, which is used for managing authentication and authorization flows. The issue occurs when a realm administrator configures client policies to enforce specific authentication requirements on confidential clients. Due to improper evaluation of the client state during an update operation, an attacker with client management permissions can bypass these security policies by first creating a public client and then updating it to a confidential client with weaker authentication. This can result in the persistence of clients that do not comply with the intended security hardening of the realm.

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 authorization services that allow administrators to restrict access to resources based on time policies (for example, only allowing access during business hours). A flaw was discovered where a user can include a fake time value in their authorization request that overrides the actual server time. This allows the user to bypass these time-based restrictions and access protected resources at unauthorized times.

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 full-scope-disabled client-policy executor within the keycloak-services component. This component is responsible for enforcing security policies during client registration and configuration in Red Hat Build of Keycloak. The issue occurs because the executor only validates the fullScopeAllowed field when it is explicitly provided in a request. By omitting this field, a delegated user can bypass the policy, resulting in a client created with full scope access. This allows the client to obtain tokens with unauthorized role mappings.

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 TokenManager component of the Keycloak identity management service. When an administrator attempts to revoke tokens for a specific application (client) using a "not-before" policy, the revocation may be silently ignored if the overall security realm already has an older, non-zero revocation policy in place. This issue can allow previously issued tokens to remain valid for refreshing sessions and accessing user information even after an administrator has attempted to invalidate them. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

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 SAML protocol implementation of Keycloak, an open-source identity and access management solution. The issue occurs when Keycloak handles SAML authentication requests using the HTTP-Redirect binding. If a client is configured with a wildcard redirect URL, an attacker can craft a request that includes malicious parameters. When a user authenticates, Keycloak appends its legitimate response to the attacker's parameters. This can cause some service providers to process the attacker's data instead of the real login information, potentially leading to a user being logged into the wrong account.

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 secure-client-uris client policy executor within Keycloak core services. This component is responsible for enforcing security requirements on client configurations, such as requiring encrypted connections for redirect URIs. Due to an improper check that only looks at the start of a web address rather than properly verifying the host, an attacker can bypass these security restrictions by using a specially crafted domain name. This could allow an attacker to intercept sensitive authentication codes over unencrypted connections.

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 Keycloak, which handles OpenID Connect (OIDC) authentication flows. The issue occurs because the security check designed to prevent HTTP parameter pollution only inspects the query portion of a redirect URL and ignores the fragment portion. When a client is configured with a wildcard redirect URI, an attacker can use this to inject duplicate security parameters into the login response. If a client application is not configured correctly, it might trust the attacker's injected data instead of the real security information from Keycloak, leading to session fixation or account confusion.

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 OIDC token introspection endpoint of the keycloak-services component. Keycloak is an open-source identity and access management solution used to secure modern applications and services. The issue occurs when a confidential client, configured to receive signed JWT introspection responses, attempts to introspect a token issued for a different audience. Although the endpoint correctly identifies the token as inactive for that client, it still returns the full set of token claims within a signed JWT field. This allows an unauthorized client to bypass audience-based restrictions and access sensitive information contained in the token.

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 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.

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 RoleContainerResource component of Keycloak. The issue occurs because certain name-based endpoints in the admin REST API do not properly enforce authorization checks when managing composite roles. This allows a delegated administrator with manage-realm permissions to remove essential child roles from built-in admin roles, potentially disrupting administrative functions within a realm.

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 client policy enforcement mechanism of Keycloak. The issue occurs when the system checks group membership by name instead of a unique identifier. An attacker with client management privileges could bypass security policies by joining a group with a matching name in a different part of the group hierarchy, potentially allowing them to register or update clients without following required security hardening profiles.

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 way to manage identity providers and organizations through its administrative API. A flaw was discovered where an administrator with permission to manage identity providers could link a new provider to an organization without having the required permissions to manage that organization. This could allow an unauthorized administrator to influence how users log into specific organizations.

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 role-users endpoint of the keycloak-services library, which is the core component of the Keycloak identity and access management solution. The issue occurs because the system fails to check if an administrator has permission to view individual users when listing members of a role. This allows a restricted administrator to see private information, such as names and email addresses, for users they should not be able to access.

Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.6 · Red Hat Build of Keycloak · Red Hat Data Grid 8

A flaw was found in the Keycloak Admin REST API, which is used to manage security realms and clients. The issue occurs when the system processes requests for rotated client secrets that are stored in a secure vault. Due to improper boundary enforcement, a delegated administrator with view-only permissions can retrieve the actual resolved secret instead of the vault placeholder, leading to the exposure of sensitive credentials.

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.

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 exists in the org.keycloak.broker.oidc package where the OIDC broker incorrectly synchronizes the email_verified claim. When an OIDC identity provider is configured with trustEmail=true and the userinfo endpoint is enabled, Keycloak retrieves the email address from the userinfo response but retrieves the email_verified status exclusively from the id_token. The root cause is a lack of validation ensuring that the email_verified claim in the id_token actually refers to the email address returned by the userinfo endpoint. If these two sources return different email addresses, the id_token's email_verified=true claim is blindly applied to the userinfo email. Exploitation Conditions: The OIDC identity provider must have trustEmail set to true (non-default). The userinfo endpoint must be enabled (default). The attacker must control or have compromised the upstream OIDC provider. Concrete Impact: Mark arbitrary email addresses as verified in the Keycloak database. Bypass email-based security controls or verification workflows. Potential account takeover if the application relies solely on the email_verified flag from the IdP to link accounts.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.14 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.5

A flaw was found in the ClientResource component of Keycloak's admin services when Fine-Grained Admin Permissions (FGAP) v2 is enabled. This issue allows a delegated administrator, who should only have limited control over specific clients, to attach or remove hidden client scopes that they are not authorized to see or manage. As a result, an attacker could inject unauthorized data or permissions into the security tokens issued to end-users, potentially tricking other applications into granting higher levels of access than intended.

Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.6 · Red Hat Build of Keycloak · Red Hat Data Grid 8

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.