CVE-2026-107623: Red Hat build of Keycloak 26.6 · Missing Authorization
Affects Red Hat build of Keycloak 26.6Source CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 21 Nov 2026, 17:34 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 4.3 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat build of Keycloak 26.6rhbk/keycloak-operator-bundle | Affected– | Fixed in– |
| Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9 | Affected– | Fixed in– |
| Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9-operator | Affected– | Fixed in– |
| Red Hat build of Keycloak 26.6.8keycloak-services | Affected– | Fixed in– |
| Red Hat build of Keycloak 26.6.8rhbk/keycloak-rhel9 | Affected– | Fixed in– |
| Red Hat Single Sign-On 7keycloak-services | Affected– | Fixed in– |
AI-suggested
Red Hat currently does not provide a mitigation that meets their criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat advisories for updates and avoid granting unnecessary client management privileges to reduce risk.
Description
A serialization bug in the OIDC Dynamic Client Registration component of Red Hat build of Keycloak 26.6 causes the backchannel logout offline token revocation setting to be omitted from responses. This omission silently disables the setting during client updates, allowing offline tokens to remain valid after user sessions are terminated via backchannel logout.