Description
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. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6.7-3 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6-20 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6-20 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6.7
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.6.7
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.6.7
Default version status: unaffected
Red Hat Red Hat Data Grid 8
Default version status: unaffected
Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
Default version status: unaffected
Red Hat Red Hat Single Sign-On 7
Default version status: unaffected