Unauthorized token issuance via omitted user-status check
Published Jan 21, 2026 · Updated Jan 21, 2026
Incorrect authorization in Red Hat build of Keycloak before 26.4.9 allows remote authenticated users to mint tokens for disabled users. The version 1 token-exchange handler resolves requested_subject but checks only that the user exists, not that the account is enabled. An internal client with impersonation permission is required; the resulting access and refresh tokens restore privileges that account deactivation had revoked.
Summary
What happened
Incorrect authorization in Red Hat build of Keycloak before 26.4.9 allows remote authenticated users to mint tokens for disabled users. The version 1 token-exchange handler resolves requested_subject but checks only that the user exists, not that the account is enabled. An internal client with impersonation permission is required; the resulting access and refresh tokens restore privileges that account deactivation had revoked.
The record
- CVE
- CVE-2025-14559
- Published
- Jan 21, 2026
- Updated
- Jan 21, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-840, T1550.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 21, 2026CVE publishedPublication date reported by the CVE source.
- Jan 21, 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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo