OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.

The remote Fedora 41 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2025-ab1fce816d advisory.

    Update to upstream 2.4.3, including fixes for CVE-2025-62513 and CVE-2025-62705.

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 42 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2025-4bf7795b4e advisory.

    Update to upstream 2.4.3, including fixes for CVE-2025-62513 and CVE-2025-62705.

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 43 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2025-0687b2debc advisory.

    Update to upstream 2.4.3, including fixes for CVE-2025-62513 and CVE-2025-62705.

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

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

  - OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao's
    audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly
    redacted (HMAC'd). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME
    verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the
    OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could
    be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry
    so are of limited long-term use. This issue has been patched in OpenBao 2.4.2. (CVE-2025-62513)

  - OpenBao is an open source identity-based secrets management system. Prior to version 2.4.2, OpenBao's
    audit log did not appropriately redact fields when relevant subsystems sent []byte response parameters
    rather than strings. This includes, but is not limited to sys/raw with use of encoding=base64, all data
    would be emitted unredacted to the audit log, and Transit, when performing a signing operation with a
    derived Ed25519 key, would emit public keys to the audit log. This issue has been patched in OpenBao
    2.4.2. (CVE-2025-62705)

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

  - OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao's
    audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly
    redacted (HMAC'd). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME
    verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the
    OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could
    be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry
    so are of limited long-term use. This issue has been patched in OpenBao 2.4.2. (CVE-2025-62513)

ID	Name	Product	Family	Severity
272139	Fedora 41 : openbao (2025-ab1fce816d)	Nessus	Fedora Local Security Checks	medium
272135	Fedora 42 : openbao (2025-4bf7795b4e)	Nessus	Fedora Local Security Checks	medium
272073	Fedora 43 : openbao (2025-0687b2debc)	Nessus	Fedora Local Security Checks	medium
435756	Alpine: multiple openbao packages: security update to 2.4.3-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	medium
435756	Alpine: multiple openbao packages: security update to 2.4.3-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	medium
435735	SCA: security update for github.com/openbao/openbao (GHSA-ghfh-fmx4-26h8)	Tenable Cloud Security	SCA Checks	medium
435735	SCA: security update for github.com/openbao/openbao (GHSA-ghfh-fmx4-26h8)	Tenable Self-Hosted Container Security	SCA Checks	medium

Detections

Analytics

CVE-2025-62513

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium