How severe is CVE-2025-55001?

CVE-2025-55001 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2025-55001 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-55001?

CVE-2025-55001 affects Openbao. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-55001?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-55001 have an EU (EUVD) identifier?

Yes. CVE-2025-55001 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-24033.

When was CVE-2025-55001 published?

CVE-2025-55001 was published on 2025-08-09 and last updated on 2026-06-17.

CVE-2025-55001

CVE-2025-55001 is a medium-severity vulnerability in Openbao with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-156.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
EPSS exploit prediction: 0% (11th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-24033
Weakness: CWE-156
Affected product: Openbao
Published: 2025-08-09
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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.
How severe is CVE-2025-55001?: CVE-2025-55001 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-55001 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-55001?: CVE-2025-55001 affects Openbao. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-55001?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-55001 have an EU (EUVD) identifier?: Yes. CVE-2025-55001 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-24033.
When was CVE-2025-55001 published?: CVE-2025-55001 was published on 2025-08-09 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*

More vulnerabilities in Openbao

CVE-2026-33757 — Critical (CVSS 9.6): OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, OpenBao does not prompt for…
CVE-2025-54997 — Critical (CVSS 9.1): OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets,…
CVE-2024-2048 — High (CVSS 8.1): Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates…
CVE-2026-42186 — High (CVSS 7.5): OpenBao is an open source identity-based secrets management system. Prior to 2.5.3, when OpenBao's initial namespace…
CVE-2025-62513 — High (CVSS 7.5): OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao's audit log…
CVE-2025-59043 — High (CVSS 7.5): OpenBao is an open source identity-based secrets management system. In OpenBao versions prior to 2.4.1, JSON objects…

All CVEs affecting Openbao →

Other CWE-156 vulnerabilities

CVE-2025-55000 — Medium (CVSS 6.5): OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets,…
CVE-2025-6013 — Medium (CVSS 6.5): Vault and Vault Enterprise’s (“Vault”) ldap auth method may not have correctly enforced MFA if username_as_alias…
CVE-2025-6014 — Medium (CVSS 6.5): Vault and Vault Enterprise’s (“Vault”) TOTP Secrets Engine code validation endpoint is susceptible to code reuse…
CVE-2025-55127 — Medium (CVSS 5.4): HackerOne community member Dao Hoang Anh (yoyomiski) has reported an improper neutralization of whitespace in the…

Browse all CWE-156 vulnerabilities →