Skip to content
Fencer Intel
medium 4.5

CVE-2025-52893 json

OpenBao May Leak Sensitive Information in Logs When Processing Malformed Data

published last yr. modified 2mo ago also BIT-openbao-2025-52893 , EUVD-2025-19112 , GHSA-8f5r-8cmq-7fmq , GO-2025-3780

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

Summary

OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. OpenBao before v2.3.0 may leak sensitive information in logs when processing malformed data. This is separate from the earlier HCSEC-2025-09 / CVE-2025-4166. This issue has been fixed in OpenBao v2.3.0 and later. Like with HCSEC-2025-09, there is no known workaround except to ensure properly formatted requests from all clients.

Patch / fix

  • go github.com/openbao/openbao/sdk/v2 2.3.0
  • bitnami openbao 2.3.0
  • linuxfoundation openbao 2.3.0
  • openbao openbao 2.3.0
  • linuxfoundation openbao_sdk 2.3.0
  • openbao openbao_sdk 2.3.0
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250730T213748-1.1
  • openbao openSUSE Tumbleweed 2.3.1-1.1

opensuse advisories openSUSE-SU-2025:15405-1openSUSE-SU-2025:15254-1

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

alpine advisories ALPINE-CVE-2025-52893

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

Is CVE-2025-52893 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 4.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
OSV 3.1 4.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/openbao/openbao/sdk/v2
<2.3.0
2.3.0
bitnami openbao
<2.3.0
2.3.0
go github.com/openbao/openbao/sdk
all versions
 no fix listed

Affected products

  • openbao openbao

Classification

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

References

Sources

Fencer Intel 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.