OpenBao leaks HTTPRawBody in Audit Logs (CVE-2025-62513)
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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenBao, an open source identity-based secrets management system, had a regression in its audit logging mechanism in versions 2.2.0 to 2.4.1. Specifically, raw HTTP bodies used by certain endpoints were not correctly redacted (HMAC'd), leading to leakage of sensitive data in audit logs. This impacts users of the ACME functionality of PKI, where short-lived ACME verification challenge codes could be exposed, and users of the OIDC issuer functionality, where authentication and token response codes along with claims could be leaked. The ACME codes are short-lived and become unusable after verification or challenge expiry. The vulnerability has been fixed in OpenBao version 2.4.2.
Potential Impact
Sensitive short-lived ACME verification challenge codes and OIDC authentication and token response data may be exposed in audit logs due to improper redaction. While ACME codes have limited long-term use due to their short validity, exposure of OIDC tokens and claims could have security implications depending on log access controls. No known exploits in the wild have been reported.
Mitigation Recommendations
A patch is available and should be applied by upgrading OpenBao to version 2.4.2 or later. Users should review audit logs for sensitive data exposure and rotate any potentially compromised tokens or credentials if applicable.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-openbao-2025-62513
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2025-62513"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
Patch Information
Threat ID: 6aa005f6acd9273b49ab63b7
Added to database: 09/08/2026, 12:56:22 UTC
Last enriched: 09/08/2026, 13:32:19 UTC
Last updated: 10/23/2026, 15:10:10 UTC
Views: 22
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.