In short
- CVE-2025-55000 is a MEDIUM (CVSS 6.5) vulnerability affecting github.com/openbao/openbao, openbao (openbao).
- Chance of exploitation in the next 30 days (EPSS): 0.24%, higher than 14.7% of all vulnerabilities.
- Fix: update to 2.3.2, 0.0.0-20250806193153-183891f8d535 or later.
| Package | Affected versions | Patched versions |
|---|
| github.com/openbao/openbao Go | ≥ 0.1.0, < 2.3.2≥ 0.1.0< 0.0.0-20250806193153-183891f8d535
| 2.3.20.0.0-20250806193153-183891f8d535
|
| openbao | < 2.3.2
| 2.3.2
|
Description
Impact
OpenBao's TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library.
Patches
OpenBao v2.3.2 will patch this issue.
In patching, codes which were not normalized (strictly N numeric digits) will now be rejected. This is a potentially breaking change.
Workarounds
TOTP code verification is a privileged action; only trusted systems should be verifying codes. Ensure that all codes are first normalized before submitting to the OpenBao endpoint.
References
This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:
NVD 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, OpenBao's TOTP secrets engine could accept valid codes multiple times rather than strictly-once. This was caused by unexpected normalization in the underlying TOTP library. To work around, ensure that all codes are first normalized before submitting to the OpenBao endpoint. TOTP code verification is a privileged action; only trusted systems should be verifying codes.
More vulnerabilities in github.com/openbao/openbao
See all →Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free