Cyber Resilience

CVE-2025-55000

Openbao ≤ 2.3.2

Published
09 August 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0021 11th percentile
Risk Priority 48 floored blend · peak EPSS

Summary

CVE-2025-55000 is a medium-severity Improper Neutralization of Whitespace (CWE-156) vulnerability in Openbao Openbao. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-156

Related Threats

CVEs Like This One

CVE-2025-55001Same product: Openbao Openbao
CVE-2025-54998Same product: Openbao Openbao
CVE-2026-33757Same product: Openbao Openbao
CVE-2026-39388Same product: Openbao Openbao
CVE-2025-54999Same product: Openbao Openbao
CVE-2025-54997Same product: Openbao Openbao
CVE-2026-39946Same product: Openbao Openbao
CVE-2025-59043Same product: Openbao Openbao
CVE-2025-52893Same product: Openbao Openbao
CVE-2026-42186Same product: Openbao Openbao

Affected Assets

openbao
openbao
≤ 2.3.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

SI-10 directly requires validation of inputs, which structurally prevents improper whitespace handling before data reaches downstream components.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization to prevent whitespace issues.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding standards directly require proper input sanitization and neutralization of special elements like whitespace.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect whitespace handling issues but does not prevent them at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes input validation and sanitization practices that can prevent improper whitespace handling.

A.8.26 Application security requirements partial match
prevents

Application security requirements typically mandate proper input validation and neutralization of special characters including whitespace.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles may indirectly support input handling but do not specifically address whitespace neutralization.

References