CVE-2025-0604: Keycloak-ldap-federation: authentication bypass due to missing ldap bind after password reset in keycloak
A flaw was found in Keycloak. When an Active Directory user resets their password, the system updates it without performing an LDAP bind to validate the new credentials against AD. This vulnerability allows users whose AD accounts are expired or disabled to regain access in Keycloak, bypassing AD restrictions. The issue enables authentication bypass and could allow unauthorized access under certain conditions.
Security readout for executives and security teams
Plain-English summary
A password reset can let some Active Directory users regain Keycloak access even when their AD accounts are expired or disabled. The reset is accepted without verifying the new password through an LDAP bind. This weakens centralized account restrictions and may expose applications protected by Keycloak.
Executive priority
Treat this as a prompt identity-control remediation, especially where Keycloak protects sensitive applications or AD disablement is the primary offboarding control. It is not rated critical, but delayed remediation could leave terminated, suspended, or expired accounts able to regain access under the stated conditions.
Technical view
CVE-2025-0604 is a CWE-287 authentication flaw in LDAP federation. After an Active Directory password reset, Keycloak can update credentials without binding to LDAP to validate them. An affected user may then bypass AD account-expiration or disablement controls. CVSS 3.1 is 5.4: network-accessible, low complexity, low privileges, no user interaction, with limited confidentiality and integrity impact.
Likely exposure
Exposure requires an affected Red Hat build, Active Directory federation, and the vulnerable password-reset path. The bundle identifies Red Hat build of Keycloak 26.0 packages at versions 26.0.10-3, 26.0-11, and 26.0-12, plus Red Hat Single Sign-On 7. Empty or contradictory version entries should be resolved against Red Hat guidance.
Exploitation context
The user must already have sufficient access to initiate the relevant password reset, but could regain application access despite AD disabling or expiring their account. The supplied sources do not establish public exploitation, and the CVE is not identified as being in KEV. No conclusion about active exploitation should be drawn beyond that evidence.
Researcher notes
The central defect is missing LDAP credential validation after password reset, creating inconsistent identity state between Keycloak and AD. The source bundle contains broad entries marked unaffected alongside explicit affected Red Hat builds; use package-level advisory data for scoping. No exploit evidence is supplied. Validate both authentication results and synchronization of AD account status.
Mitigation direction
Inventory Keycloak and Red Hat Single Sign-On versions and identify LDAP-federated Active Directory realms.
Review RHSA-2025:2544 and RHSA-2025:2545 for applicable corrected packages and deployment instructions.
Apply the relevant Red Hat update after testing authentication and federation behavior.
Until remediated, closely monitor password resets and subsequent access involving disabled or expired AD accounts.
Validation and detection
Confirm deployed package names and versions against the explicit affected entries and Red Hat advisories.
Verify whether affected realms use Active Directory through LDAP federation and permit password resets.
In an authorized test environment, confirm AD-disabled or expired users cannot regain access after resetting passwords.
Review identity logs for password resets followed by successful access from accounts disabled or expired in AD.
After updating, repeat federation, password-reset, and account-disablement regression tests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-287 · source CWE mapping
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.