A flaw was found in the OIDC protocol implementation of Keycloak, an open-source identity and access management solution. The issue occurs during the token refresh process when the server restores requested audiences from stored client IDs. Keycloak fails to verify if the target audience client is still enabled before issuing a new access token. This allows an application with an existing refresh token to continue obtaining valid access tokens for a disabled client, potentially bypassing administrative access controls for resource servers that rely on offline JWT validation.
CVE-2026-93999
Score 4.2 from GitHub Security Advisory published 2026-09-19. a secondary CVSS source baseline 4.2; 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
- 4.2
- EG Score
- 4.2(high)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity42% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
September 19, 2026
Last Modified
September 22, 2026
Advisory Details (2)
Auto-updated Sep 19, 20262537165 – (CVE-2026-93999) CVE-2026-93999 keycloak-services: keycloak-services: Token refresh continues issuing tokens for disabled audience clients
https://bugzilla.redhat.com/show_bug.cgi?id=2537165CVE-2026-93999 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-93999Vendor Advisories for CVE-2026-93999(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 21× in last 7d / 21× 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-09-24 22:59 UTCEG score recompute
- 2026-09-24 22:59 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 21:15 UTCEG score recompute
- 2026-09-23 21:15 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 19:53 UTCGHSA enrichment
- 2026-09-22 16:23 UTCEG score recompute
- 2026-09-22 16:23 UTCGHSA enrichment
- 2026-09-22 16:06 UTCEG score recompute
- 2026-09-22 16:06 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 18:13 UTCEG score recompute
- 2026-09-21 18:13 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 16:50 UTCEG score recompute
- 2026-09-20 16:50 UTCGHSA enrichment
- 2026-09-19 15:28 UTCEG score recompute
- 2026-09-19 14:25 UTCEG score recompute
- 2026-09-19 14:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-93999?
When was CVE-2026-93999 disclosed?
Is CVE-2026-93999 actively exploited?
What is the CVSS score of CVE-2026-93999?
How do I remediate CVE-2026-93999?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93999
Is Your Infrastructure Affected by CVE-2026-93999?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.