CVE-2025-55000 | OpenBao TOTP Secrets Engine Enables Code Reuse

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.

Published: 2025-08-09 Last update: 2025-11-13 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-55000 is rated Low Risk (31.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-55000

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-25 0.02% 0.05% +0.04%
2 2025-08-09 0.02%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-55000

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 3.6 [email protected]

Weakness enumeration for CVE-2025-55000

GitHub Security Advisory for CVE-2025-55000

GHSA-f7c3-mhj2-9pvg · Severity: medium · Ecosystem: go — OpenBao TOTP Secrets Engine Code Reuse

OS Trackers for CVE-2025-55000

vendor priority summary link
alpine CVE-2025-55000: 1 source package rows (openbao); 20 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 18. https://security.alpinelinux.org/vuln/CVE-2025-55000

Affected software / configurations for CVE-2025-55000

Vendor Product Version Raw CPE
openbao openbao < 2.3.2 cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*

References for CVE-2025-55000

cvelogic Threat Intelligence