CVE-2025-54998: OpenBao Userpass and LDAP User Lockout Bypass
Impact
Attackers could bypass the automatic user lockout mechanisms in the OpenBao Userpass or LDAP auth systems. This was caused by different aliasing between pre-flight and full login request user entity alias attributions.
Patches
OpenBao v2.3.2 will patch this issue.
Workarounds
Existing users may apply rate-limiting quotas on the authentication endpoints: https://openbao.org/api-docs/system/rate-limit-quotas/
References
This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:
- https://discuss.hashicorp.com/t/hcsec-2025-16-vault-userpass-and-ldap-user-lockout-bypass/76035 - https://nvd.nist.gov/vuln/detail/CVE-2025-6004
Other sources
OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, attackers could bypass the automatic user lockout mechanisms in the OpenBao Userpass or LDAP auth systems. This was caused by different aliasing between pre-flight and full login request user entity alias attributions. This is fixed in version 2.3.2. To work around this issue, existing users may apply rate-limiting quotas on the authentication endpoints:, see https://openbao.org/api-docs/system/rate-limit-quotas/.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-54998?
The severity of CVE-2025-54998 is considered critical due to the potential for attackers to bypass user lockout mechanisms.
How do I fix CVE-2025-54998?
To fix CVE-2025-54998, upgrade to OpenBao version 2.3.2 or later.
What software is affected by CVE-2025-54998?
CVE-2025-54998 affects OpenBao versions from 0.1.0 up to but not including 2.3.2.
What are the implications of CVE-2025-54998?
The implications of CVE-2025-54998 include the risk of unauthorized access due to ineffective user lockout mechanisms.
Is there a workaround for CVE-2025-54998?
No official workarounds have been provided for CVE-2025-54998; upgrading to the latest version is recommended.