Skip to main content
VulnerabilityPublished Updated

CVE-2026-18218: Missing Authorization

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-18218· Medium 4.2

Not known to be exploited · CVSS 4.2 Medium : update Red Hat build of Keycloak 26.6 when convenient.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat build of Keycloak 26.6Affected–Fixed in–
Red HatRed Hat build of Keycloak 26.6Affected–Fixed in–
Red HatRed Hat build of Keycloak 26.6.7Affected–Fixed in–
Red HatRed Hat Data Grid 8Affected–Fixed in–
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackAffected–Fixed in–
Red HatRed Hat Single Sign-On 7Affected–Fixed in–

AI-suggested

Red Hat has released fixed versions of Keycloak 26.6.7 images for OpenShift Container Platform. Users should update to these fixed versions to remediate the vulnerability. Before applying updates, back up existing installations including applications, configuration files, and databases. No other mitigation or workaround is indicated in the vendor advisories.

Description

A vulnerability in the TokenManager component of Keycloak allows token revocation attempts for specific clients to be silently ignored if the realm has an older, non-zero revocation policy. This flaw permits previously issued tokens to remain valid, enabling session refresh and access to user information despite administrative revocation attempts. The issue is tracked as CVE-2026-18218 with a medium severity score of 4.2. Red Hat has released fixed versions in Keycloak 26.6.7 images for OpenShift deployments.

References

Community reviews

Loading reviews…