CVE-2026-18208: Missing Authorization
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium : update Red Hat Build of Keycloak when convenient.
Data as of 6 Nov 2026, 14:04 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 31 Jul 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 6 Nov 2026.
What to do
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat build of Keycloak 26.6.8rhbk-openshift-rhel9/rhbk-openshift-rhel9 | Affected– | Fixed in– |
| Red Hat Build of Keycloakkeycloak-services | Affected– | Fixed in– |
| Red Hat Build of Keycloakrhbk-keycloak-rhel9/rhbk-keycloak-rhel9 | Affected– | Fixed in– |
| Red Hat Data Grid 8keycloak-services | Affected– | Fixed in– |
| Red Hat JBoss Enterprise Application Platform Expansion Packkeycloak-services | Affected– | Fixed in– |
| Red Hat Single Sign-On 7keycloak-services | Affected– | Fixed in– |
AI-suggested
A security update is available in Red Hat build of Keycloak version 26.6.8, which addresses this and multiple other vulnerabilities. Users should upgrade to this fixed version to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Description
A vulnerability in the OIDC token introspection endpoint of the keycloak-services component allows a confidential client to receive full token claims for tokens issued to different audiences. Although the token is marked inactive for the unauthorized client, the endpoint still returns sensitive token claims within a signed JWT. This flaw enables unauthorized clients to bypass audience-based restrictions and access sensitive information.