Red Hat OIDC protocol implementation of Keycloak: missing authorization
Medium4.2CVE-2026-93999 · Published Sep 19, 2026 · updated Sep 22, 2026
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.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| Red Hat Build of Keycloak Product | all versions | No fix yet |
| all versions | No fix yet | |
| all versions | No fix yet | |
| Red Hat Single Sign-On 7 Product | all versions | No fix yet |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- Severity from
- the vendor (its own CVE record or advisory)
- Weakness
- CWE-862
More Red Hat advisories
All Red Hat| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Sep 19 | Red Hat Admin REST API of Keycloak: missing authorization | Medium6.6 | No fix yet |
| Sep 19 | Red Hat Admin REST API of Keycloak: missing authorization | Medium6.5 | No fix yet |
| Sep 18 | Red Hat OpenShift Container Platform 4: server-side request forgery | Critical9.3 | No fix yet |
| Sep 18 | Red Hat Netty: request smuggling | Medium6.5 | No fix yet |
| Sep 18 | Red Hat Netty: request smuggling | Medium6.5 | No fix yet |
| Sep 18 | A flaw was found in cockpit-files | Medium6.1 | No fix yet |