CVE-2025-55000 Details
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.
A vulnerability in OpenBao's TOTP secrets engine, present in versions 0.1.0 prior to 2.3.1, allows valid TOTP codes to be accepted multiple times instead of just once. This issue arises from unanticipated normalization in the TOTP library used by OpenBao. TOTP code verification is a privileged action, and only trusted systems should validate these codes.
Users should upgrade to OpenBao version 2.3.2, where this vulnerability is fixed. After upgrading, ensure that TOTP codes are normalized to remove any whitespace before submission. TOTP code verification should only be performed by trusted systems.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Aug 11, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-156 | Improper Neutralization of Whitespace | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| openbao openbao | < 2.3.2 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 13, 2025 | Reanalysis | [email protected] |
| Aug 12, 2025 | Initial Analysis | [email protected] |
| Aug 9, 2025 | New CVE Received | [email protected] |