CVE-2025-62513 OpenBao leaks HTTPRawBody in Audit Logs
OpenBao fails to redact raw HTTP bodies in audit logs, potentially leaking ACME challenge codes and OIDC tokens to anyone with log access.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2025-62513?
CVE-2025-62513 is a medium-severity vulnerability in openbao, published on 22 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao's audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC'd). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.
Weakness: CWE-532
Which versions are affected by CVE-2025-62513?
4 open source packages ship an affected version, including github.com/openbao/openbao and openbao. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/openbao/openbao Go | From 0.0.0-20241114205727-b1235e585db7 | 0.0.0-20251022165510-cc2c476bac66 |
github.com/openbao/openbao Go | From 0.0.0-20241114205727-b1235e585db7 | 0.0.0-20251022165510-cc2c476bac66 |
github.com/openbao/openbao Go | From 0.0.0-20241114205727-b1235e585db7 | 0.0.0-20251022165510-cc2c476bac66 |
openbao Bitnami | From 2.2.0 | 2.4.2 |
Products include Openbao Openbao.
How do I fix CVE-2025-62513?
Upgrade github.com/openbao/openbao to 0.0.0-20251022165510-cc2c476bac66 or later.
Is CVE-2025-62513 being exploited?
There is no known exploitation of CVE-2025-62513 in the wild and no public exploit code.
Other vulnerabilities in openbao
- CVE-2026-33757 OpenBao lacks user confirmation for OIDC direct callback mode
- CVE-2026-33758 OpenBao has Reflected XSS in its OIDC authentication error message
- CVE-2025-54997 OpenBao: Privileged Operator May Execute Code on the Underlying Host
- CVE-2025-64761 OpenBao Privileged Operator Identity Group Root Escalation
- CVE-2025-59043 OpenBao vulnerable to denial of service via malicious JSON request processing
Sources
Also known as BIT-openbao-2025-62513, GHSA-ghfh-fmx4-26h8, GO-2025-4049.