CVE-2025-55001 json
OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias
published 2025-08-08 15 mo ago modified 2026-09-08 2 mo ago also BIT-openbao-2025-55001 , EUVD-2025-24033 , GHSA-2q8q-8fgw-9p6p , GO-2025-3859
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 2.3.1 and below, OpenBao allowed the assignment of policies and MFA attribution based upon entity aliases, chosen by the underlying auth method. When the username_as_alias=true parameter in the LDAP auth method was in use, the caller-supplied username was used verbatim without normalization, allowing an attacker to bypass alias-specific MFA requirements. This issue was fixed in version 2.3.2. To work around this, remove all usage of the username_as_alias=true parameter and update any entity aliases accordingly.
Patch / fix
- go github.com/openbao/openbao 0.0.0-20250807212521-c52795c1ef74, 2.3.2
- bitnami openbao 0.0.0-20250807212521-c52795c1ef74, 2.3.2
- openbao openbao 0.0.0-20250807212521-c52795c1ef74, 2.3.2
- govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250814T182633-150000.1.98.1
suse advisories SUSE-SU-2025:02912-1
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20250811T192933-1.1
opensuse advisories openSUSE-SU-2025:15434-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 14 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/openbao/openbao | >=0.1.0, <2.3.2 <0.0.0-20250807212521-c52795c1ef74 >=0.1.0 |
2.3.2 0.0.0-20250807212521-c52795c1ef74 |
| bitnami | openbao | <0.0.0-20250807212521-c52795c1ef74 >=0.0.1, <2.3.2 |
0.0.0-20250807212521-c52795c1ef74 2.3.2 |
Affected products
- openbao openbao
Classification
- Weakness
-
- CWE-156 Improper Neutralization of Whitespace
References
-
github.com
/openbao/openbao/commit/c52795c1ef746c7f2c510f9225aa8ccbbd44f9fc
web, patch
-
github.com
/openbao/openbao/security/advisories/GHSA-2q8q-8fgw-9p6p
web, vendor-advisory, advisory
-
discuss.hashicorp.com
/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-username-as-alias/76092
web, not-applicable
-
nvd.nist.gov
/vuln/detail/CVE-2025-55001
advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2025-6013
advisory, web
-
github.com
/openbao/openbao
package
Sources
- CVE List CVE-2025-55001
- GitHub Advisory GHSA-2q8q-8fgw-9p6p
- NVD CVE-2025-55001
- OSV BIT-openbao-2025-55001
- OSV GO-2025-3859
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.