CVE-2025-62513: Github.com/openbao/openbao OpenBao Leaks HTTPRawBody Vulnerability

MODERATE
Advisory Identifier: GHSA-ghfh-fmx4-26h8
Share
CWE-532
Published
Advisory Summary

CVE-2025-62513 is a MODERATE openbao leaks httprawbody vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Github.com/openbao/openbao libraries in the Go ecosystem. The issue involves openbao leaks httprawbody in audit logs. Remediation is available by upgrading affected packages to version 0.0.0-20251022165510-cc2c476bac66.

CVE-2025-62513 at a Glance

CVE Identifier CVE-2025-62513
GHSA Identifier GHSA-ghfh-fmx4-26h8
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Github.com/openbao/openbao
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2025-62513

To remediate this vulnerability, upgrade all affected Github.com/openbao/openbao dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/openbao/openbao fixed: 0.0.0-20251022165510-cc2c476bac66 
Upgrade github.com/openbao/openbao to 0.0.0-20251022165510-cc2c476bac66
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/openbao/openbao

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-62513, inspect your project dependencies for Github.com/openbao/openbao:

inspect dependencies for github.com/openbao/openbao

Analyze the terminal output to locate any version of Github.com/openbao/openbao in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20251022165510-cc2c476bac66), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Github.com/openbao/openbao, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact OpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd). This impacted the following subsystems: - When using the ACME functionality of PKI, this would result in short-lived ACME verification challenge codes being leaked in the audit logs. - When using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. Third-party plugins may be affected. ### Patches OpenBao v2.4.2 will patch this issue. ### Workarounds If users do not use the above functionality, they are not impacted. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use.

CVE-2025-62513 Affected Github.com/openbao/openbao Versions

1 component(s)
Fixed Versions:
0.0.0-20251022165510-cc2c476bac66
Product / Package Ecosystem Affected Versions Fixed Version
github.com/openbao/openbao
golang/github.com/openbao/openbao
Go
≥ 0.0.0-20241114205727-b1235e585db7
< 0.0.0-20251022165510-cc2c476bac66
0.0.0-20251022165510-cc2c476bac66

References

GitHub Advisory / Wiki ADVISORY
https://github.com/openbao/openbao/security/advisories/GHSA-ghfh-fmx4-26h8
NVD — CVE-2025-62513 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-62513
Security Fix Commit FIX COMMIT
https://github.com/openbao/openbao/commit/cc2c476bac66e1d94776c2629793daec3af625f8
Github.com/openbao/openbao Source Repository REPOSITORY
https://github.com/openbao/openbao

Frequently Asked Questions

What is CVE-2025-62513?
CVE-2025-62513 is a security vulnerability in Github.com/openbao/openbao involving OpenBao leaks HTTPRawBody in Audit Logs under CWE-532: Insertion of Sensitive Information into Log File.
Which Github.com/openbao/openbao versions are affected?
Affected versions include releases prior to 0.0.0-20251022165510-cc2c476bac66 across affected packages: github.com/openbao/openbao.
What version fixes CVE-2025-62513?
Upgrading to 0.0.0-20251022165510-cc2c476bac66 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/openbao/openbao affected?
Yes, github.com/openbao/openbao is affected in releases prior to 0.0.0-20251022165510-cc2c476bac66. Upgrade your dependency to 0.0.0-20251022165510-cc2c476bac66 or later.
What CWE is associated with CVE-2025-62513?
CVE-2025-62513 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check Go dependencies for CVE-2025-62513?
Run the dependency tree command: 'inspect dependencies for github.com/openbao/openbao'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ghfh-fmx4-26h8",
  "modified" : "2025-10-23T17:38:22Z",
  "published" : "2025-10-22T19:37:53Z",
  "aliases" : [ "CVE-2025-62513" ],
  "summary" : "OpenBao leaks HTTPRawBody in Audit Logs",
  "details" : "### Impact\n\nOpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd).  This impacted the following subsystems:\n\n - When using the ACME functionality of PKI, this would result in short-lived ACME verification challenge codes being leaked in the audit logs.\n - When using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs.\n\nThird-party plugins may be affected.\n\n### Patches\n\nOpenBao v2.4.2 will patch this issue.\n\n### Workarounds\n\nIf users do not use the above functionality, they are not impacted. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openbao/openbao"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.0.0-20241114205727-b1235e585db7"
      }, {
        "fixed" : "0.0.0-20251022165510-cc2c476bac66"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openbao/openbao/security/advisories/GHSA-ghfh-fmx4-26h8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-62513"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openbao/openbao/commit/cc2c476bac66e1d94776c2629793daec3af625f8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openbao/openbao"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-22T19:37:53Z",
    "nvd_published_at" : "2025-10-22T20:15:38Z"
  }
}