Recherche « Red Hat build of Keycloak 26.6.3 »

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

A flaw was found in Keycloak's ClientRegistrationAuth component. A remote unauthenticated attacker can exploit this vulnerability by sending a specially crafted POST request with a malformed 'Authorization: Bearer' header to any client registration endpoint. This can lead to an ArrayIndexOutOfBoundsException, causing the server to return an HTTP 500 error and resulting in a Denial of Service (DoS) for the affected service.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

A flaw was found in Keycloak. When revokeRefreshToken=true is enabled and persistent session storage is in use, a server restart can reset internal timing mechanisms. This allows a remote attacker, who has previously captured a user's refresh token, to replay that token even after it has been revoked. Successful exploitation grants the attacker unauthorized access to the victim's account, potentially leading to information disclosure or privilege escalation.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

A flaw was found in Keycloak. A remote attacker with high privileges, such as a realm administrator configuring a malicious Lightweight Directory Access Protocol (LDAP) server or an attacker compromising an upstream LDAP server, could exploit this vulnerability. By sending a malformed LDAP password policy response during a password authentication request, the attacker can trigger an OutOfMemoryError. This causes the Keycloak Java Virtual Machine (JVM) to terminate, leading to a denial of service (DoS) for all realms on the affected node.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

A flaw was found in Keycloak. A remote, unauthenticated attacker can exploit this vulnerability by sending specially crafted SOAP requests to the SAML ECP (Security Assertion Markup Language Enhanced Client or Proxy) endpoint with varying client IDs. By observing distinct faultstrings in the responses, the attacker can determine the client's protocol type, leading to information disclosure.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

A flaw was found in Keycloak's Client Policies, specifically within the `org.keycloak.protocol.oidc` component. When certain condition providers (client-type, client-roles, client-attributes, client-scopes) are used to enforce security restrictions, the `reject-ropc-grant` executor is silently bypassed. This allows an unauthenticated remote attacker to obtain tokens via a Resource Owner Password Credentials (ROPC) grant, even when a policy is explicitly configured to block it. This bypass can lead to unauthorized access and information disclosure.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

A flaw was found in Keycloak. An authenticated user with existing organization membership can exploit this flaw by accessing user-facing APIs, such as the account API or by requesting an OpenID Connect (OIDC) token with the 'organization' scope. This allows organization metadata to be disclosed in tokens, even after an administrator has explicitly disabled the Organizations feature, potentially leading to incorrect authorization decisions by resource servers.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

A flaw was found in Keycloak. When both realm-level and client-level `notBefore` revocation policies are configured, Keycloak's OpenID Connect (OIDC) Introspection feature fails to properly honor the realm-level policy. This allows tokens that should have been revoked to remain active, potentially leading to unauthorized access or continued session validity. This could impact the security of systems utilizing Keycloak for identity and access management.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

A flaw was found in Keycloak. An authenticated user can bypass configured WebAuthn policies during credential registration by manipulating client-side JavaScript. This occurs because the server-side processAction() fails to validate that the newly created credential's parameters, such as public key algorithms, match the realm's configured WebAuthn policies. This could lead to the creation of credentials that do not adhere to administrative security requirements, potentially weakening the overall security posture of the system by allowing non-compliant authentication methods.

Red Hat build of Keycloak 26.4 · Red Hat build of Keycloak 26.4.13 · Red Hat build of Keycloak 26.6 · Red Hat build of Keycloak 26.6.3

When Keycloak is started with `--features-disabled=account,account-api`, the Account REST API is only partially disabled. Five endpoints under the versioned path `/account/v1alpha1` remain fully functional — including both read and write operations — because they lack the `checkAccountApiEnabled()` gate that correctly blocks four other endpoints in the same REST service class. The user needs to have permissions to use the API.