CVE-2025-52893 Details
Description
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.
A vulnerability in OpenBao prior to version 2.3.0 may lead to the unintentional leakage of sensitive information in logs. This occurs when the application processes malformed data, creating a risk of exposing secrets, certificates, or keys. The issue has been addressed in OpenBao version 2.3.0 and later. Users are advised to ensure that all client requests are properly formatted, as no specific workaround exists for this vulnerability.
Users can update to OpenBao version 2.3.0 or later to address this vulnerability. After updating, it is recommended to review server and audit logs for any exposed sensitive information. If any matches are found, rotating the affected secret is advised.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 25, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-532 | Insertion of Sensitive Information into Log File | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| openbao openbao | < 2.3.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Aug 12, 2025 | Initial Analysis | [email protected] |
| Jun 25, 2025 | New CVE Received | [email protected] |