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

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.

Published: 2025-08-09 Last update: 2025-08-12 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-55001 is rated Moderate Risk (40/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.18%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-55001

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-05 0.05% 0.18% +0.13%
2 2026-04-25 0.01% 0.05% +0.04%
3 2025-08-09 — 0.01% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-55001

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 5.2 [email protected]

Weakness enumeration for CVE-2025-55001

GitHub Security Advisory for CVE-2025-55001

GHSA-2q8q-8fgw-9p6p · Severity: medium · Ecosystem: go — OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias

OS Trackers for CVE-2025-55001

vendor priority summary link
alpine medium CVE-2025-55001: 1 source package rows (openbao); 18 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 18. https://security.alpinelinux.org/vuln/CVE-2025-55001

Affected software / configurations for CVE-2025-55001

Vendor Product Version Raw CPE
openbao openbao < 2.3.2 cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*

References for CVE-2025-55001

cvelogic Threat Intelligence