CVE-2025-55003: OpenBao Login MFA Bypasses Rate Limiting and TOTP Token Reuse

Published Aug 8, 2025
·
Updated

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.

Patches

OpenBao v2.3.2 will patch this issue.

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:

- https://discuss.hashicorp.com/t/hcsec-2025-19-vault-login-mfa-bypass-of-rate-limiting-and-totp-token-reuse/76038 - https://nvd.nist.gov/vuln/detail/CVE-2025-6015

Other sources

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'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. This issue was fixed in version 2.3.2. To work around this, use of rate-limiting quotas can limit an attacker's ability to exploit this: https://openbao.org/api-docs/system/rate-limit-quotas/.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/openbao/openbao<0.0.0-20250807113757-8340a6918f6c
0.0.0-20250807113757-8340a6918f6c
go/github.com/openbao/openbao>=0.1.0<2.3.2
2.3.2

Event History

Aug 8, 2025
Advisory Published
via GitHub·02:44 PM
Data Sourced
via GitHub·02:44 PM
DescriptionSeverityWeaknessAffected Software
Aug 9, 2025
CVE Published
via MITRE·02:01 AM
Data Sourced
via MITRE·02:01 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-55003?

CVE-2025-55003 has a critical severity rating due to its capability to bypass authentication rate limiting.

2

How do I fix CVE-2025-55003?

To fix CVE-2025-55003, update OpenBao to version 0.0.0-20250807113757-8340a6918f6c or 2.3.2.

3

What impact does CVE-2025-55003 have on users?

CVE-2025-55003 may allow unauthorized access to user accounts by bypassing the Multi-Factor Authentication system.

4

Which versions of OpenBao are affected by CVE-2025-55003?

OpenBao versions prior to 0.0.0-20250807113757-8340a6918f6c and between 0.1.0 and 2.3.2 are affected by CVE-2025-55003.

5

Is there a known exploit for CVE-2025-55003?

Yes, there is a potential exploit for CVE-2025-55003 that allows attackers to bypass authentication mechanisms.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203