Skip to content
Fencer Intel
medium 4.2

CVE-2026-18218 json

Keycloak-services: keycloak-services: client not-before revocation ignored when realm not-before is older but nonzero

published 3mo ago modified last mo. also BIT-keycloak-2026-18218 , EUVD-2026-51478

cvss
4.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

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. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Patch / fix

  • bitnami keycloak 26.7.3
  • Red Hat Red Hat build of Keycloak 26.6 26.6-20, 26.6.7-3

Is CVE-2026-18218 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-18218 updated cvss 4.2

keycloak-services: keycloak-services: Client not-before revocation ignored when realm not-before is older but nonzero

  • Red Hat build of Keycloak 26.6 rhbk/keycloak-rhel9 26.6-20, rhbk/keycloak-rhel9-operator 26.6-20, rhbk/keycloak-operator-bundle 26.6.7-3
    fixed: vendor fix RHSA-2026:68277
  • Red Hat build of Keycloak 26.6.7
    fixed: vendor fix RHSA-2026:68278
  • Red Hat Data Grid 8 keycloak-services 23.0.7 Red Hat JBoss Enterprise Application Platform Expansion Pack keycloak-services 23.0.7 Red Hat Single Sign-On 7 keycloak-services 23.0.7
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.2 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OSV 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami keycloak
<26.7.3
26.7.3

Affected products

  • Red Hat Red Hat build of Keycloak 26.6
  • Red Hat Red Hat build of Keycloak 26.6.7
  • Red Hat Red Hat Data Grid 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
  • Red Hat Red Hat Single Sign-On 7

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.