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.
CVE-2026-18208
Score 6.5 from GitHub Security Advisory published 2026-07-31. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
July 31, 2026
Last Modified
July 31, 2026
Advisory Details (2)
Auto-updated Jul 31, 20262508304 – (CVE-2026-18208) CVE-2026-18208 keycloak-services: keycloak-services: Inactive out-of-audience token introspection leaks signed JWT claim
https://bugzilla.redhat.com/show_bug.cgi?id=2508304Vendor Advisories for CVE-2026-18208(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 22:47 UTCEG score recompute
- 2026-08-01 22:47 UTCGHSA enrichment
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 20:23 UTCEG score recompute
- 2026-07-31 20:23 UTCGHSA enrichment
- 2026-07-31 19:48 UTCEG score recompute
- 2026-07-31 19:48 UTCGHSA enrichment
- 2026-07-31 08:18 UTCEG score recompute
- 2026-07-31 07:28 UTCEG score recompute
- 2026-07-31 07:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-18208?
When was CVE-2026-18208 disclosed?
Is CVE-2026-18208 actively exploited?
What is the CVSS score of CVE-2026-18208?
How do I remediate CVE-2026-18208?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18208
Is Your Infrastructure Affected by CVE-2026-18208?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.