# CVE-2025-62705: GO-2025-4052 - OpenBao and Vault Leak []byte Fields in Audit Logs in github.com/openbao/openbao

Source: https://junglewise.ai/threats/cve-2025-62705-openbao-and-vault-leak-byte-fields-in-audit-logs  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-10-22  
License: CC BY 4.0 with a link back

CVE-2025-62705 · Severity: medium · CVSS 4.9 · Published 2025-10-22

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.

Technologies: [github.com/openbao/openbao (Go)](https://junglewise.ai/threats/technologies/github-com-openbao-openbao), [OpenBao](https://junglewise.ai/threats/technologies/openbao). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [OpenBao](https://junglewise.ai/threats/vendors/openbao).

## Quick answers

**Is CVE-2025-62705 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-62705 being exploited in the wild.

**How severe is CVE-2025-62705?** Medium severity, with a CVSS score of 4.9, published 22 October 2025.

**Which products and versions are affected?** github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=0.0.0-20251022165510-cc2c476bac66.

**Is there a fix for CVE-2025-62705?** Yes. github.com/openbao/openbao (Go): upgrade to 0.0.0-20251022165510-cc2c476bac66 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-62705?** Check whether you run github.com/openbao/openbao (Go) or OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/openbao/openbao (Go): upgrade to 0.0.0-20251022165510-cc2c476bac66 or later

  ```sh
  go get github.com/openbao/openbao@v0.0.0-20251022165510-cc2c476bac66
  ```


## Affected products

- github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=0.0.0-20251022165510-cc2c476bac66
- OpenBao

## Identifiers

- CVE-2025-62705
- GHSA-rc54-2g2c-g36g
- GO-2025-4052

## Related threats

- [OpenBao policy cache incorrect authorization via namespace traversal](https://junglewise.ai/threats/cve-2026-115365-openbao-from-2-3-0-before-2-6-3-contains-an-incorrect)
- [OpenBao ACL bypass in policy denial evaluation](https://junglewise.ai/threats/cve-2026-115361-openbao-before-2-6-3-contains-an-acl-bypass-vulnerability-that)
- [OpenBao Kubernetes Auth token renewal on revoked credentials](https://junglewise.ai/threats/cve-2026-115356-openbao-before-2-6-4-and-2-7-x-before-2-7-1-does-not-verify-when)
- [OpenBao Agent information disclosure via stdout in exec rendering mode](https://junglewise.ai/threats/cve-2026-77285-openbao-agent-information-disclosure-via-stdout-in-exec-rendering)
- [OpenBao recovery mode timing attack token leakage](https://junglewise.ai/threats/cve-2026-63132-openbao-recovery-mode-timing-attack-token-leakage)