cve.bz

CVE-2025-62705 openbao openbao

5.7 mediumEPSS 0.3%Fix available

Medium (5.7) in openbao openbao. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/openbao/openbao 0.0.0-20251022165510-cc2c476bac66.

On this page
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.

Severity

CVSS 4.0

5.7 medium
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

CVSS 3.1

4.9 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-62705 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-62705?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-62705?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-62705 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openbao:openbaobefore 2.4.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rc54-2g2c-g36gGogithub.com/openbao/openbao<0.0.0-20251022165510-cc2c476bac660.0.0-20251022165510-cc2c476bac66
GO-2025-4052Gogithub.com/openbao/openbao<0.0.0-20251022165510-cc2c476bac660.0.0-20251022165510-cc2c476bac66

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedgovulncheck-vulndb0.0.20251105T184115-1.1openSUSE-SU-2025:15710-1
openSUSETumbleweedopenbao2.4.3-1.1openSUSE-SU-2025:15663-1
Alpinev3.22, v3.23, v3.24openbao2.4.3-r0ALPINE-CVE-2025-62705

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE · Alpine.

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON