How severe is CVE-2025-54999?

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

Is CVE-2025-54999 being actively exploited?

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

What products are affected by CVE-2025-54999?

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

How do I fix CVE-2025-54999?

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

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

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

When was CVE-2025-54999 published?

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

CVE-2025-54999

CVE-2025-54999 is a low-severity vulnerability in Openbao with a CVSS 3.x base score of 3.7. 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-203.

Key facts

Severity: Low (CVSS 3.x base score 3.7)
EPSS exploit prediction: 0% (8th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-24035
Weakness: CWE-203
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 0.1.0 through 2.3.1, when using OpenBao's userpass auth method, user enumeration was possible due to timing difference between non-existent users and users with stored credentials. This is independent of whether the supplied credentials were valid for the given user. This issue was fixed in version 2.3.2. To work around this issue, users may use another auth method or apply rate limiting quotas to limit the number of requests in a period of time: https://openbao.org/api-docs/system/rate-limit-quotas/.

Frequently asked questions

What is CVE-2025-54999?: OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, when using OpenBao's userpass auth method, user enumeration was possible due to timing difference between non-existent users and users with stored credentials. This is independent of whether the supplied credentials were valid for the given user. This issue was fixed in version 2.3.2. To work around this issue, users may use another auth method or apply rate limiting quotas to limit the number of requests in a period of time: https://openbao.org/api-docs/system/rate-limit-quotas/.
How severe is CVE-2025-54999?: CVE-2025-54999 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2025-54999 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-54999?: CVE-2025-54999 affects Openbao. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-54999?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-54999 have an EU (EUVD) identifier?: Yes. CVE-2025-54999 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-24035.
When was CVE-2025-54999 published?: CVE-2025-54999 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-203 (Observable Discrepancy) vulnerabilities

CVE-2019-25337 — Critical (CVSS 9.8): OwnCloud 8.1.8 contains a username enumeration vulnerability that allows remote attackers to discover user accounts by…
CVE-2026-23519 — Critical (CVSS 9.8): RustCrypto CMOV provides conditional move CPU intrinsics which are guaranteed on major platforms to execute in…
CVE-2025-27667 — Critical (CVSS 9.8): Vasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.843 Application 20.0.1923 allows Administrative…
CVE-2024-25714 — Critical (CVSS 9.8): In Rhonabwy through 1.1.13, HMAC signature verification uses a strcmp function that is vulnerable to side-channel…
CVE-2024-25191 — Critical (CVSS 9.8): php-jwt 1.0.0 uses strcmp (which is not constant time) to verify authentication, which makes it easier to bypass…
CVE-2024-25190 — Critical (CVSS 9.8): l8w8jwt 2.2.1 uses memcmp (which is not constant time) to verify authentication, which makes it easier to bypass…

Browse all CWE-203 (Observable Discrepancy) vulnerabilities →