Description
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 logout when browser cookies are missing. As a result, one user may receive tokens that belong to another user.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Keycloak keycloak
Default version status: unaffected
0 to < 26.0.0affected
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2.11-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2-12 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2-12 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2.11
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4.4-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-3 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-3 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4.4
Default version status: unaffected
References
- https://access.redhat.com/errata/RHSA-2025:21370 ↗
- https://access.redhat.com/errata/RHSA-2025:21371 ↗
- https://access.redhat.com/errata/RHSA-2025:22088 ↗
- https://access.redhat.com/errata/RHSA-2025:22089 ↗
- https://access.redhat.com/security/cve/CVE-2025-12390 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2406793 ↗
- https://github.com/keycloak/keycloak/issues/43853 ↗