CVE-2025-55001
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.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 6.5
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
- EPSS probability
- 0.22%
- CWE
- CWE-156
- Published
- 2025-08-09
- Last modified
- 2026-03-12
Affected products
- openbao openbao
Weakness type
Related vulnerabilities
- CVE-2025-55000 — OpenBao TOTP Secrets Engine Enables Code Reuse
- CVE-2025-6013 — Vault LDAP MFA Enforcement Bypass When Using Username As Alias
- CVE-2025-6014 — Vault TOTP Secrets Engine Code Reuse