Unauthenticated account lockout via conflicting email registration
Published Feb 27, 2024 · Updated Nov 21, 2025
Account lockout in Keycloak 23.0.5 allows remote attackers to prevent targeted users from logging in by registering a conflicting email. The self-registration flow accepts a new account whose email equals an existing user's email-format username, causing username authentication to resolve the conflicting identity and deny the original account. Exploitation requires enabled self-registration, a victim whose username and registered email differ, and knowledge of that username; authentication by registered email remains available.
Summary
What happened
Account lockout in Keycloak 23.0.5 allows remote attackers to prevent targeted users from logging in by registering a conflicting email. The self-registration flow accepts a new account whose email equals an existing user's email-format username, causing username authentication to resolve the conflicting identity and deny the original account. Exploitation requires enabled self-registration, a victim whose username and registered email differ, and knowledge of that username; authentication by registered email remains available.
The record
- CVE
- CVE-2024-1722
- Published
- Feb 27, 2024
- Updated
- Nov 21, 2025
- Vendor
- Red Hat
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-645, T1531
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 2025Record 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.
Weakness, pattern, technique
Public exploit references
- Red Hat Bugzilla account-conflict reproduction procedurefunctional · demonstrated
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