CVE-2025-54998
OpenBao Userpass and LDAP User Lockout Bypass
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/.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
OpenBao Userpass and LDAP User Lockout Bypass
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/.
- Record
CVE-2025-54998- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-307
- Updated
- 2026-11-02
EUVDEUVD-2025-24036
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/.
- Record
EUVD-2025-24036- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-j3xv-7fxp-gfhx
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:
- Record
GHSA-j3xv-7fxp-gfhx- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-307
- Updated
- 2026-11-02
NVD
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/.
- Record
CVE-2025-54998- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-307
- Updated
- 2026-11-02
OSVALPINE-CVE-2025-54998
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/.
- Record
ALPINE-CVE-2025-54998- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-03
OSV
OpenBao Userpass and LDAP User Lockout Bypass
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/.
- Record
CVE-2025-54998- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-307
- Updated
- 2026-11-02
Show 5 moreShow less
OSVGHSA-j3xv-7fxp-gfhx
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:
- Record
GHSA-j3xv-7fxp-gfhx- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-307
- Updated
- 2026-11-02
OSVBIT-openbao-2025-54998 No score
OpenBao Userpass and LDAP User Lockout Bypass
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/.
- Record
BIT-openbao-2025-54998- Updated
- 2026-11-02
OSVGO-2025-3855 No score
OpenBao Userpass and LDAP User Lockout Bypass in github.com/openbao/openbao
OpenBao Userpass and LDAP User Lockout Bypass in github.com/openbao/openbao.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/openbao/openbao before v2.3.2.
- Record
GO-2025-3855- Updated
- 2026-11-02
OSVopenSUSE-SU-2025:15434-1 No score
govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media
These are all security issues fixed in the govulncheck-vulndb-0.0.20250811T192933-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2025:15434-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:02912-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20250814T182633 2025-08-14T18:26:33Z (jsc#PED-11136)
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-3765 CVE-2024-44906 GHSA-h4h6-vccr-44h2
- GO-2025-3829 CVE-2025-54410 GHSA-4vq8-7jfc-9cvp
-
Update to version 0.0.20250811T192933 2025-08-11T19:29:33Z (jsc#PED-11136)
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-3822 CVE-2025-53942 GHSA-9g4j-v8w5-7x42
- GO-2025-3829 CVE-2025-54410 GHSA-4vq8-7jfc-9cvp
- GO-2025-3830 CVE-2025-54388 GHSA-x4rx-4gw3-53p4
- GO-2025-3831 CVE-2025-50738 GHSA-hfcf-79gh-f3jc
- GO-2025-3832 CVE-2021-21411 GHSA-652x-m2gr-hppm
- GO-2025-3833 CVE-2025-54576 GHSA-7rh7-c77v-6434
- GO-2025-3834 CVE-2025-54424 GHSA-8j63-96wh-wh3j
- GO-2025-3835 CVE-2025-54386 GHSA-q6gg-9f92-r9wg
- GO-2025-3836 CVE-2025-6037 GHSA-6c5r-4wfc-3mcx
- GO-2025-3837 CVE-2025-5999 GHSA-6h4p-m86h-hhgh
- GO-2025-3838 CVE-2025-6000 GHSA-mr4h-qf9j-f665
- GO-2025-3839 CVE-2025-6011 GHSA-mwgr-84fv-3jh9
- GO-2025-3840 CVE-2025-6004 GHSA-qgj7-fmq2-6cc4
- GO-2025-3841 CVE-2025-6014 GHSA-qv3p-fmv3-9hww
- GO-2025-3842 CVE-2025-6015 GHSA-v6r4-35f9-9rpw
- GO-2025-3843 CVE-2025-8341 GHSA-3c93-92r7-j934
- GO-2025-3844 CVE-2025-53534 GHSA-fm3m-jrgm-5ppg
- GO-2025-3845 CVE-2025-54801 GHSA-qx2q-88mx-vhg7
- GO-2025-3847 CVE-2025-54799 GHSA-q82r-2j7m-9rv4
- GO-2025-3848 CVE-2025-6013 GHSA-7rx2-769v-hrwf
- GO-2025-3851 CVE-2025-44779 GHSA-93jv-pvg8-hf3v
- GO-2025-3852 CVE-2025-7195 GHSA-856v-8qm2-9wjv
- GO-2025-3853 CVE-2025-55000 GHSA-f7c3-mhj2-9pvg
- GO-2025-3854 CVE-2025-54999 GHSA-hh28-h22f-8357
- GO-2025-3855 CVE-2025-54998 GHSA-j3xv-7fxp-gfhx
- GO-2025-3856 CVE-2025-55003 GHSA-rxp7-9q75-vj3p
- GO-2025-3857 CVE-2025-54996 GHSA-vf84-mxrq-crqc
- GO-2025-3858 CVE-2025-54997 GHSA-xp75-r577-cvhp
- GO-2025-3859 CVE-2025-55001 GHSA-2q8q-8fgw-9p6p
-
Update to version 0.0.20250807T150727 2025-08-07T15:07:27Z (jsc#PED-11136)
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-3849 CVE-2025-47907
- Record
SUSE-SU-2025:02912-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/openbao/openbaoGo |
0.1.0 up to 2.3.2 | 2.3.2 |
github.com/openbao/openbaoGo |
before 0.0.0-20250807212521-c52795c1ef74 | 0.0.0-20250807212521-c52795c1ef74 |
openbaoAlpine:v3.22 |
before 2.3.2-r0 | 2.3.2-r0 |
openbaoAlpine:v3.23 |
before 2.3.2-r0 | 2.3.2-r0 |
openbaoAlpine:v3.24 |
before 2.3.2-r0 | 2.3.2-r0 |
openbaoBitnami |
before 0.0.0-20250807212521-c52795c1ef74, 0.0.1 up to 2.3.2 | 0.0.0-20250807212521-c52795c1ef742.3.2 |
github.com/openbao/openbaoGo |
before 0.0.0-20250807212521-c52795c1ef74, 0.1.0 and later | 0.0.0-20250807212521-c52795c1ef74 |
govulncheck-vulndbSUSE:Linux Enterprise Module for Package Hub 15 SP6 |
before 0.0.20250814T182633-150000.1.98.1 | 0.0.20250814T182633-150000.1.98.1 |
govulncheck-vulndbopenSUSE:Leap 15.6 |
before 0.0.20250814T182633-150000.1.98.1 | 0.0.20250814T182633-150000.1.98.1 |
govulncheck-vulndbopenSUSE:Tumbleweed |
before 0.0.20250811T192933-1.1 | 0.0.20250811T192933-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, aliases, references | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-54998 is a medium vulnerability (CVSS 5.3) in Openbao, published August 8, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.23%, the 14th percentile. Fixed in github.com/openbao/openbao 2.3.2.
References
github.com/openbao/openbao/security/advisories/GHSA-j3xv-7fxp-gfhx
discuss.hashicorp.com/t/hcsec-2025-16-vault-userpass-and-ldap-user-lockout-bypass/76035
nvd.nist.gov/vuln/detail/CVE-2025-6004
Show 35 moreShow less
security.alpinelinux.org/vuln/CVE-2025-54998
suse.com/support/update/announcement/2025/suse-su-202502912-1