Account lockout bypass via unchecked CIBA status
Published May 28, 2026 · Updated May 28, 2026
Authentication bypass in Red Hat build of Keycloak allows remote attackers to obtain tokens for temporarily locked accounts through CIBA. The CIBA authentication endpoint omits the account lockout-status check and issues a valid token after the user approves the request. Exploitation requires non-default CIBA enablement, a configured confidential client, valid client credentials, and approval on the user’s authentication device.
Summary
What happened
Authentication bypass in Red Hat build of Keycloak allows remote attackers to obtain tokens for temporarily locked accounts through CIBA. The CIBA authentication endpoint omits the account lockout-status check and issues a valid token after the user approves the request. Exploitation requires non-default CIBA enablement, a configured confidential client, valid client credentials, and approval on the user’s authentication device.
The record
- CVE
- CVE-2026-9798
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-305, T1110
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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