The issue arises because Keycloak does not perform an LDAP bind after a password reset, leading to potential authentication bypass for expired or disabled AD accounts. A fix should enforce LDAP validation after password updates to ensure consistency with AD authentication policies.
This issue has been addressed in the following products: Red Hat build of Keycloak 22 Via RHSA-2025:2545 https://access.redhat.com/errata/RHSA-2025:2545
This issue has been addressed in the following products: Red Hat build of Keycloak 26.0 Via RHSA-2025:2544 https://access.redhat.com/errata/RHSA-2025:2544