Cyber Resilience

CVE-2025-54999

Openbao ≤ 2.3.2

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

Summary

CVE-2025-54999 is a low-severity Observable Discrepancy (CWE-203) vulnerability in Openbao Openbao. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Account Discovery (T1087); ranked at the 9th 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 IA-6 (Authentication Feedback) and SI-11 (Error Handling) — 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, when using OpenBao's userpass auth method, user enumeration was possible due to timing difference between non-existent…

more

users and users with stored credentials. This is independent of whether the supplied credentials were valid for the given user. This issue was fixed in version 2.3.2. To work around this issue, users may use another auth method or apply rate limiting quotas to limit the number of requests in a period of time: https://openbao.org/api-docs/system/rate-limit-quotas/.

CWE(s)
CWE-203

Related Threats

MITRE ATT&CK Enterprise Techniques

T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1595 Active Scanning Reconnaissance
Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-55003Same product: Openbao Openbao
CVE-2025-54998Same product: Openbao Openbao
CVE-2026-39388Same product: Openbao Openbao
CVE-2025-59043Same product: Openbao Openbao
CVE-2026-42186Same product: Openbao Openbao
CVE-2025-64761Same product: Openbao Openbao
CVE-2025-62705Same product: Openbao Openbao
CVE-2026-39946Same product: Openbao Openbao
CVE-2026-33757Same product: Openbao Openbao
CVE-2025-54996Same product: Openbao Openbao

Affected Assets

openbao
openbao
≤ 2.3.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

IA-6 Authentication Feedback good match

Obscures authentication feedback so that success/failure differences are not observable to attackers.

SI-11 Error Handling good match

Requires error messages to avoid revealing exploitable details, directly stopping observable response discrepancies.

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 prevent observable response discrepancies via consistent error handling and timing.

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.17 Clock synchronization none match
none

Accurate, synchronized timestamps reduce observable timing discrepancies that an attacker could exploit to infer sensitive information or distinguish between success and failure paths.

References