Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Openbao | Openbao | >= 2.2.0, < 2.4.2 |
Related Weaknesses (CWE)
References
- https://github.com/openbao/openbao/commit/cc2c476bac66e1d94776c2629793daec3af625Patch
- https://github.com/openbao/openbao/security/advisories/GHSA-ghfh-fmx4-26h8Vendor Advisory
FAQ
What is CVE-2025-62513?
CVE-2025-62513 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 corr...
How severe is CVE-2025-62513?
CVE-2025-62513 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-62513?
Check the references section above for vendor advisories and patch information. Affected products include: Openbao Openbao.