CVE-2025-0604
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceKeycloak fails to perform an LDAP bind validation against Active Directory after a password reset, allowing users with expired or disabled AD accounts to regain access through Keycloak. This authentication bypass occurs because the password update happens without verifying the new credentials against AD account status.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Keycloak LDAP/AD integrationReview Keycloak user federation settings to determine if LDAP or Active Directory is configured as the user storage provider. Check the realm settings under 'User federation' section.Affected if LDAP or Active Directory user federation is configured and enabled
-
Confirm password reset is enabledCheck Keycloak realm authentication flows and password policies to verify that password reset or update functionality is available to LDAP-federated users.Affected if Password reset/update is enabled for LDAP users
-
Check LDAP bind validation configurationExamine the LDAP federation provider settings in Keycloak for the 'Validate password' or 'LDAP bind after password change' configuration option. This is typically found in the user federation LDAP settings.Affected if LDAP bind validation after password change is not enabled or is set to 'false'
-
Verify AD account status checkReview Keycloak LDAP configuration to determine if the provider checks account status (enabled/disabled/expired) when binding with new credentials after a password reset.Affected if Account status validation against AD is not performed after password changes
-
Compare installed Keycloak versionCheck the running Keycloak version through the server info endpoint or server logs and compare against any published affected version ranges from the CVE advisory.Affected if The installed version falls within the affected range and LDAP/AD integration is in use
If Keycloak is integrated with LDAP/Active Directory and allows password resets without performing LDAP bind validation to verify account status, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataConfigure Keycloak to perform LDAP bind validation after password reset to verify new credentials against AD and check account status (enabled/disabled/expired) before allowing password changes.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0604 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0604 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data