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.
CVE-2025-55001
MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EPSS
- 12.6%
- KEV
- Not listed
Published
August 9, 2025
Last Modified
August 12, 2025
References (3)
- security-advisories@githubhttps://discuss.hashicorp.com/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-username-as-alias/76092
- security-advisories@githubhttps://github.com/openbao/openbao/commit/c52795c1ef746c7f2c510f9225aa8ccbbd44f9fc
- security-advisories@githubhttps://github.com/openbao/openbao/security/advisories/GHSA-2q8q-8fgw-9p6p
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/openbao/openbao | — | 0.0.0-20250807212521-c52795c1ef74 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2025-55001?
CVE-2025-55001 is a medium vulnerability published on August 9, 2025. 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…
When was CVE-2025-55001 disclosed?
CVE-2025-55001 was first published in the National Vulnerability Database on August 9, 2025, with the most recent update on August 12, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-55001 actively exploited?
CVE-2025-55001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-55001?
CVE-2025-55001 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2025-55001?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-55001, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-55001
Is Your Infrastructure Affected by CVE-2025-55001?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.