Vulnerability in github.com/openbao/openbao (CVE-2025-62705)
Summary
Vulnerability in github.com/openbao/openbao (CVE-2025-62705). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.0-20251022165510-cc2c476bac66 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2025-62705 was discovered in github.com/openbao/openbao.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "github.com/openbao/openbao CVE-2025-62705".
CVE-2025-62705 (github.com/openbao/openbao). Severity: Info. Category: CWE-532.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2025-62705) in github.com/openbao/openbao. A serious software flaw has been identified.
Target versions of github.com/openbao/openbao (see vendor advisory). If running in production, identify exposure immediately.
Severity: Info. Low severity or not yet rated.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-532)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- web nvd.nist.gov