CVE-2025-54999
3.7 · LOWOverview
CVE-2025-54999 is a low-severity vulnerability affecting openbao openbao. It was published on August 9, 2025 and has a CVSS 3.1 base score of 3.7 (LOW).
This vulnerability has a CVSS 3.1 base score of 3.7, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical 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/.
Remediation
Check the references section for vendor advisories and patches from openbao. Update openbao to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| openbao | openbao | >= 0, < 2.3.2 | Affected |
References
Frequently Asked Questions
What is CVE-2025-54999?
CVE-2025-54999 is a low-severity vulnerability affecting openbao openbao. It was published on August 9, 2025 and has a CVSS 3.1 base score of 3.7 (LOW).
How severe is CVE-2025-54999?
This vulnerability has a CVSS 3.1 base score of 3.7, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2025-54999?
Check the references section for vendor advisories and patches from openbao. Update openbao to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2025-54999?
CyberStrike's AI-powered security agents can automatically detect CVE-2025-54999 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2025
View all →Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerabi
A vulnerability has been found in Union Bank of India Vyom 8.0.34 on Android and classified as probl
Symlink following in the installer for Zoom Workplace App for macOS before 6.2.10 may allow an authe
In DA, there is a possible out of bounds read due to a missing bounds check. This could lead to loca
HCL Connections Docs is vulnerable to a sensitive information disclosure which could allow a user to
The MongoDB Shell may be susceptible to control character injection where an attacker with control o
Android apps can load web pages using the Custom Tabs feature. This feature supports a transition an
Information Exposure vulnerability in Hitachi JP1/IT Desktop Management 2 - Smart Device Manager on
A vulnerability has been identified in the libarchive library. This flaw involves an integer overflo
A vulnerability has been identified in the libarchive library. This flaw can be triggered when file
handcraftedinthealps goodby-csv is a highly memory efficient, flexible and extendable open-source CS
A vulnerability, which was classified as problematic, has been found in TOTOLINK T10 4.1.8cu.5207. A