Summary
Workarounds
Use of rate-limiting quotas can limit an attacker's ability to exploit this: https://openbao.org/api-docs/system/rate-limit-quotas/
References
This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:
Impact
OpenBao's Login Multi-Factor Authentication (MFA) system allows enforcing MFA using Time-based One Time Password (TOTP). Due to normalization applied by the underlying TOTP library, codes were accepted which could contain whitespace; this whitespace could bypass internal rate limiting of the MFA method and allow reuse of existing MFA codes.
CVE-2025-55003 has a CVSS score of 5.7 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.2, 0.0.0-20250807113757-8340a6918f6c); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
OpenBao v2.3.2 will patch this issue.
Frequently Asked Questions
- What is CVE-2025-55003? CVE-2025-55003 is a medium-severity security vulnerability in github.com/openbao/openbao (go), affecting versions >= 0.1.0, < 2.3.2. It is fixed in 2.3.2, 0.0.0-20250807113757-8340a6918f6c.
- How severe is CVE-2025-55003? CVE-2025-55003 has a CVSS score of 5.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/openbao/openbao are affected by CVE-2025-55003? github.com/openbao/openbao (go) versions >= 0.1.0, < 2.3.2 is affected.
- Is there a fix for CVE-2025-55003? Yes. CVE-2025-55003 is fixed in 2.3.2, 0.0.0-20250807113757-8340a6918f6c. Upgrade to this version or later.
- Is CVE-2025-55003 exploitable, and should I be worried? Whether CVE-2025-55003 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-55003 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-55003?
- Upgrade
github.com/openbao/openbaoto 2.3.2 or later - Upgrade
github.com/openbao/openbaoto 0.0.0-20250807113757-8340a6918f6c or later
- Upgrade