CVE-2025-54998 Details
Description
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/.
A vulnerability exists in OpenBao versions 0.1.0 prior to 2.3.1, allowing attackers to bypass the automatic user lockout mechanisms in the Userpass and LDAP authentication systems. This issue arises from inconsistent handling of user entity aliases between pre-flight and full login requests, enabling exploitation by manipulating username casing. The vulnerability is addressed in OpenBao version 2.3.2.
Users can upgrade to OpenBao version 2.3.2, which addresses this vulnerability. Alternatively, rate-limiting quotas can be applied to the authentication endpoints.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Aug 11, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-307 | Improper Restriction of Excessive Authentication Attempts | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| openbao openbao | < 2.3.2 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 13, 2025 | Reanalysis | [email protected] |
| Aug 12, 2025 | Initial Analysis | [email protected] |
| Aug 9, 2025 | New CVE Received | [email protected] |