Red Hat Red Hat build of Keycloak 26.4.4 vulnerabilities (CVE)

CVE records published for Red Hat Red Hat build of Keycloak 26.4.4, newest first. Follow to get an email when a new one appears.

5 results
3.1Low
CVE-2025-12150

Org.keycloak/keycloak-services: webauthn attestation statement verification bypass

Keycloak keycloak; Red Hat Red Hat build of Keycloak 26.2; Red Hat Red Hat build of Keycloak 26.2.11; Red Hat Red Hat build of Keycloak 26.4

A flaw was found in Keycloak’s WebAuthn registration component. This vulnerability allows an attacker to bypass the configured attestation policy and register untrusted or forged authenticators via submission of an attestation object with fmt: "none", even wh…

6.8Medium
CVE-2025-11538

Keycloak-server: debug default bind address

Keycloak keycloak; Red Hat Red Hat build of Keycloak 26.4; Red Hat Red Hat build of Keycloak 26.4.4

A vulnerability exists in Keycloak's server distribution where enabling debug mode (--debug <port>) insecurely defaults to binding the Java Debug Wire Protocol (JDWP) port to all network interfaces (0.0.0.0). This exposes the debug port to the local network, …

6.0Medium
CVE-2025-12390

Org.keycloak.protocol.oidc.endpoints.logoutendpoint: offline session takeover due to reused authentication session id

Keycloak keycloak; Red Hat Red Hat build of Keycloak 26.2; Red Hat Red Hat build of Keycloak 26.2.11; Red Hat Red Hat build of Keycloak 26.4

A flaw was found in Keycloak. In Keycloak where a user can accidentally get access to another user's session if both use the same device and browser. This happens because Keycloak sometimes reuses session identifiers and doesn’t clean up properly during logou…

5.4Medium
CVE-2025-12110

Keycloak: org.keycloak:keycloak-services: user can refresh offline session even after client's offline_access scope was removed

Keycloak keycloak; Red Hat Red Hat build of Keycloak 26.2; Red Hat Red Hat build of Keycloak 26.2.11; Red Hat Red Hat build of Keycloak 26.4

A flaw was found in Keycloak. An offline session continues to be valid when the offline_access scope is removed from the client. The refresh token is accepted and you can continue to request new tokens for the session. As it can lead to a situation where an a…