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


- **Severity:** Medium 4.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Jun 2025
- **Updated:** 25 Jun 2025
- **Also known as:** BIT-openbao-2025-52893, CLEANSTART-2026-WB07116, GHSA-8f5r-8cmq-7fmq, GO-2025-3780, UBUNTU-CVE-2025-52893

## What is CVE-2025-52893?

CVE-2025-52893 is a medium-severity vulnerability in openbao, published on 25 Jun 2025. 

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-52893?

5 open source packages ship an affected version, including github.com/openbao/openbao/sdk/v2, openbao and github.com/openbao/openbao/sdk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openbao/openbao/sdk/v2` | Go | All versions | 2.3.0 |
| `github.com/openbao/openbao/sdk/v2` | Go | All versions | 2.3.0 |
| `github.com/openbao/openbao/sdk/v2` | Go | All versions | 2.3.0 |
| `openbao` | Bitnami | All versions | 2.3.0 |
| `github.com/openbao/openbao/sdk` | Go | All versions | None |

Products: Openbao Openbao.

## How do I fix CVE-2025-52893?

Upgrade github.com/openbao/openbao/sdk/v2 to 2.3.0 or later.

## Is CVE-2025-52893 being exploited?

There is no known exploitation of CVE-2025-52893 in the wild and no public exploit code.

## Other vulnerabilities in openbao

- [CVE-2026-33757](https://insights.sbomify.com/CVE-2026-33757/): OpenBao lacks user confirmation for OIDC direct callback mode (critical 9.6)
- [CVE-2026-33758](https://insights.sbomify.com/CVE-2026-33758/): OpenBao has Reflected XSS in its OIDC authentication error message (critical 9.4)
- [CVE-2025-54997](https://insights.sbomify.com/CVE-2025-54997/): OpenBao: Privileged Operator May Execute Code on the Underlying Host (critical 9.1)
- [CVE-2025-64761](https://insights.sbomify.com/CVE-2025-64761/): OpenBao Privileged Operator Identity Group Root Escalation (high 7.5)
- [CVE-2025-59043](https://insights.sbomify.com/CVE-2025-59043/): OpenBao vulnerable to denial of service via malicious JSON request processing (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52893 and fix it if it is affected.

What it is: CVE-2025-52893 is a medium-severity vulnerability in openbao, published on 25 Jun 2025. 
Exploitation: There is no known exploitation of CVE-2025-52893 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openbao/openbao/sdk/v2 (Go): affected all versions; fixed in 2.3.0
- github.com/openbao/openbao/sdk/v2 (Go): affected all versions; fixed in 2.3.0
- github.com/openbao/openbao/sdk/v2 (Go): affected all versions; fixed in 2.3.0
- openbao (Bitnami): affected all versions; fixed in 2.3.0
- github.com/openbao/openbao/sdk (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52893/ (Markdown: https://insights.sbomify.com/CVE-2025-52893/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52893
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52893
- OSV: https://osv.dev/vulnerability/CVE-2025-52893

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52893/
Summaries are generated and may contain mistakes; the official description above is the record.