Medium [CVE-2026-18208] Inactive out-of-audience token introspection leaks signed JWT claim
This medium-severity Red Hat Linux advisory covers CVE-2026-18208 affecting Red Hat Build of Keycloak.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in the OIDC token introspection endpoint of the keycloak-services component. Keycloak is an open-source identity and access management solution used to secure modern applications and services.
The issue occurs when a confidential client, configured to receive signed JWT introspection responses, attempts to introspect a token issued for a different audience. Although the endpoint correctly identifies the token as inactive for that client, it still returns the full set of token claims within a signed JWT field.
This allows an unauthorized client to bypass audience-based restrictions and access sensitive information contained in the token.
The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires the attacker to control a confidential client within the same realm and possess a valid token issued for a different audience.
Successful exploitation allows an attacker to recover sensitive token claims that should be restricted by audience-based access controls. The vulnerability's root cause is a failure to sanitize the signed JWT field in the introspection response when a token is determined to be inactive due to an audience mismatch.
Weakness: CWE-862. Affected Red Hat products: Red Hat Build of Keycloak.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.