Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
AC:H reflects the mandatory pre-existing realm revocation policy prerequisite; PR:L because a valid token is required; no availability impact applies.
Primary rating from Vendor (redhat).
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Lifecycle Timeline
3DescriptionNVD
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. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
AnalysisAI
Token revocation bypass in Keycloak's TokenManager component allows sessions and user data access to persist after administrative invalidation. The flaw (CWE-862: Missing Authorization) causes client-level 'not-before' revocation policies to be silently skipped when a realm-level revocation policy with an older, non-zero timestamp is already in place - causing the revocation to produce no effect. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires all of the following to be true simultaneously: (1) the attacker or user holds a valid Keycloak refresh token or access token issued before the administrator's revocation attempt, (2) the Keycloak security realm has a pre-existing non-zero 'not-before' timestamp set at the realm level from a prior revocation action, (3) the administrator targets only the client (application) level for the new revocation without also updating the realm-level policy, and (4) the existing realm-level timestamp predates the intended client-level revocation time. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.2 score with vector AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N reflects a meaningful but conditional risk. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | During a security incident, an administrator revokes tokens for a compromised service account in a specific client application using the Keycloak admin console's 'not-before' push. Because the realm was configured with an older non-zero revocation policy from a prior administrative action, the new client-level revocation is silently skipped by TokenManager. … |
| Remediation | Administrators should apply vendor-released patches for Red Hat Build of Keycloak, Red Hat Single Sign-On 7, and the affected JBoss EAP Expansion Pack components; exact patched versions are not specified in the available data and must be confirmed via the Red Hat Security Advisory at https://access.redhat.com/security/cve/CVE-2026-18218 and Bugzilla entry https://bugzilla.redhat.com/show_bug.cgi?id=2508313. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Red Hat Build Of Keycloak
View allAccount takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML
Account takeover in Red Hat Build of Keycloak allows an unauthenticated attacker to abuse the reset-credentials flow in
Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge
Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privil
Authorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con
URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to re
Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accou
Token exchange in Keycloak bypasses Google Workspace domain allowlist restrictions, enabling any valid Google account ho
Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re
Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Micro
Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to aut
Open redirect in Red Hat build of Keycloak permits remote attackers to send victims to attacker-controlled hosts by abus
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-51478
GHSA-vhxw-j6h3-48jm