OpenBao and Vault Leak []byte Fields in Audit Logs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.7 · 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 · score source

EPSS

• CVE-2025-62705: 0.33% estimated exploitation activity in the next 30 days; percentile 26.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. - Transit, when performing a signing operation with a derived Ed25519 key, would emit public keys to the audit log. Third-party plugins may be affected. This issue has been present since HashiCorp Vault and continues to impact Vault as of v1.20.4. Patches OpenBao v2.4.2 will patch this issue. Workarounds If users do not use the above functionality, they are not impacted. To prohibit the use of sys/raw globally, ensure rawstorageendpoint=false is set or missing from the server configuration.

Published by the source

22 Oct 2025, 19:55 UTC

Last modified by the source

23 Oct 2025, 17:40 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rc54-2g2c-g36g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-62705

Advisory: OpenBao and Vault Leak []byte Fields in Audit Logs
IDs: CVE-2025-62705, GHSA-rc54-2g2c-g36g
Record: https://patchnext.com/advisories/cve-2025-62705 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openbao/openbao 0.0.0-20251022165510-cc2c476bac66. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openbao/openbao: affected < 0.0.0-20251022165510-cc2c476bac66; fixed in 0.0.0-20251022165510-cc2c476bac66

## Suggested inspection (read-only)
- Go github.com/openbao/openbao: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openbao/openbao.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rc54-2g2c-g36g (GitHub-reviewed advisory GHSA-rc54-2g2c-g36g lists affected ranges: Go github.com/openbao/openbao >=0 <0.0.0-20251022165510-cc2c476bac66)

Commands are suggestions: review each one before running it.