Authenticated access-control bypass via stale audience restoration
Published Sep 19, 2026 · Updated Sep 19, 2026
Missing authorization in Red Hat build of Keycloak allows remote authenticated users to retain access through disabled audience clients. Token refresh restores audience claims from stored client IDs without rechecking whether each target client remains enabled. Exploitation requires a previously issued refresh token and affects resources that accept the resulting JWT without online validation.
Summary
What happened
Missing authorization in Red Hat build of Keycloak allows remote authenticated users to retain access through disabled audience clients. Token refresh restores audience claims from stored client IDs without rechecking whether each target client remains enabled. Exploitation requires a previously issued refresh token and affects resources that accept the resulting JWT without online validation.
The record
- CVE
- CVE-2026-93999
- Published
- Sep 19, 2026
- Updated
- Sep 19, 2026
- Vendor
- Commonhaus Foundation
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-862, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 19, 2026CVE publishedPublication date reported by the CVE source.
- Sep 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started