CVE-2025-52893 | OpenBao May Leak Sensitive Information in Logs When Processing Malformed Data

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.

Published: 2025-06-25 Last update: 2025-08-12 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-52893 is rated Low Risk (25.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.07%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-52893

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-21 0.02% 0.07% +0.05%
2 2025-06-26 — 0.02% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-52893

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 0.9 3.6 [email protected]

Weakness enumeration for CVE-2025-52893

GitHub Security Advisory for CVE-2025-52893

GHSA-8f5r-8cmq-7fmq · Severity: medium · Ecosystem: go — OpenBao Inserts Sensitive Information into Log File when processing malformed data

OS Trackers for CVE-2025-52893

vendor priority summary link
alpine — CVE-2025-52893: 1 source package rows (openbao); 14 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 12. https://security.alpinelinux.org/vuln/CVE-2025-52893
ubuntu medium CVE-2025-52893 medium priority: Ubuntu including 1 source packages (golang-github-go-viper-mapstructure), 6 status rows across 6 suites (jammy, noble, oracular, plucky, questing, upstream): DNE 3, needs-triage 2, ignored 1. https://ubuntu.com/security/CVE-2025-52893

Affected software / configurations for CVE-2025-52893

Vendor Product Version Raw CPE
openbao openbao < 2.3.0 cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*

References for CVE-2025-52893

cvelogic Threat Intelligence