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 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/.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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 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/. (CVE-2025-54999)

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - 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 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/. (CVE-2025-54999)

  - OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including
    secrets, certificates, and keys. In versions 2.3.1 and below, accounts with access to highly-privileged
    identity entity systems in root namespaces were able to increase their scope directly to the root policy.
    While the identity system allowed adding arbitrary policies, which in turn could contain capability grants
    on arbitrary paths, the root policy was restricted to manual generation using unseal or recovery key
    shares. The global root policy was not accessible from child namespaces. This issue is fixed in version
    2.3.2. To workaround this vulnerability, use of denied_parameters in any policy which has access to the
    affected identity endpoints (on identity entities) may be sufficient to prohibit this type of attack.
    (CVE-2025-54996)

  - OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including
    secrets, certificates, and keys. In versions 2.3.1 and below, some OpenBao deployments intentionally limit
    privileged API operators from executing system code or making network connections. However, these
    operators can bypass both restrictions through the audit subsystem by manipulating log prefixes. This
    allows unauthorized code execution and network access that violates the intended security model. This
    issue is fixed in version 2.3.2. To workaround, users can block access to sys/audit/* endpoints using
    explicit deny policies, but root operators cannot be restricted this way. (CVE-2025-54997)

  - 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, attackers could bypass the automatic
    user lockout mechanisms in the OpenBao Userpass or LDAP auth systems. This was caused by different
    aliasing between pre-flight and full login request user entity alias attributions. This is fixed in
    version 2.3.2. To work around this issue, existing users may apply rate-limiting quotas on the
    authentication endpoints:, see https://openbao.org/api-docs/system/rate-limit-quotas/. (CVE-2025-54998)

ID	Name	Product	Family	Type	Severity
437061	SCA: security update for github.com/openbao/openbao (GHSA-hh28-h22f-8357)	Tenable Cloud Security	SCA Checks	Local	low
437061	SCA: security update for github.com/openbao/openbao (GHSA-hh28-h22f-8357)	Tenable Self-Hosted Container Security	SCA Checks	Local	low
435758	Alpine: multiple openbao packages: security update to 2.3.2-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	low
435758	Alpine: multiple openbao packages: security update to 2.3.2-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	low

Detections

Analytics

CVE-2025-54999

low

Tenable Plugins

low

low

low

low