Vulnerability · Published Aug 9, 2025 · Assigned by GitHub_M

CVE-2025-55001OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias

Medium 6.5

In plain English

A medium-severity security flaw in openbao from openbao. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 16% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)6.5Medium
Exploit odds (30 days)0.2%top 84.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/openbao/openbao2.3.2GHSA-2q8q-8fgw-9p6p
Gogithub.com/openbao/openbao0.0.0-20250807212521-c52795c1ef74GHSA-2q8q-8fgw-9p6p
Gogithub.com/openbao/openbao0.0.0-20250807212521-c52795c1ef74GO-2025-3859

Affected products (as reported)

VendorProductVersions
openbao openbao < 2.3.2

Weakness: CWE-156 · Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

References