Skip to content
Fencer Vulns
medium 4.9

CVE-2025-62705 json

OpenBao and Vault Leak []byte Fields in Audit Logs

published 2025-10-22 12 mo ago modified 2026-10-19 21 d ago also BIT-openbao-2025-62705 , EUVD-2025-35629 , GHSA-rc54-2g2c-g36g , GO-2025-4052

cvss
4.9
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/openbao/openbao 0.0.0-20251022165510-cc2c476bac66
  • bitnami openbao 2.4.2
  • openbao openbao 2.4.2
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20251105T184115-1.1
  • openbao openSUSE Tumbleweed 2.4.3-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15710-1openSUSE-SU-2025:15663-1

  • openbao Alpine 3.24, Alpine 3.23, Alpine 3.22 2.4.3-r0

alpine advisories ALPINE-CVE-2025-62705

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-62705 updated cvss 4.9

openbao: OpenBao and Vault Leak []byte Fields in Audit Logs

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
12 mo ago

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 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
CNA 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/openbao/openbao
<0.0.0-20251022165510-cc2c476bac66
0.0.0-20251022165510-cc2c476bac66
bitnami openbao
<2.4.2
2.4.2

Affected products

  • openbao openbao

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.