Answer in brief
CVE-2026-18208 records a Medium severity (CVSS 6.5) vulnerability in Keycloak-services: keycloak-services: inactive out-of-audience token introspection leaks signed jwt claim. The current sources do not mark it as known exploited. The current feed maps Red Hat/keycloak-services (generic), Red Hat/rhbk-keycloak-rhel9/rhbk-keycloak-rhel9 (generic), Red Hat/rhbk-openshift-rhel9/rhbk-openshift-rhel9 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/keycloak-services (generic), Red Hat/rhbk-keycloak-rhel9/rhbk-keycloak-rhel9 (generic), Red Hat/rhbk-openshift-rhel9/rhbk-openshift-rhel9 (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/keycloak-servicesgeneric | * | Not reported |
| Red Hat/rhbk-keycloak-rhel9/rhbk-keycloak-rhel9generic | * | Not reported |
| Red Hat/rhbk-openshift-rhel9/rhbk-openshift-rhel9generic | * | Not reported |
Published upstream
Jul 31, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 3, 2026
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.
Quoted source text, attributed separately from HOL analysis.