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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/openbao/openbao/commit/cc2c476bac66e1d94776c2629793daec3af625f8 Patch
- https://github.com/openbao/openbao/security/advisories/GHSA-ghfh-fmx4-26h8 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.7 · openbaoNVD modified 2026-10-19 16:10
Affected (CPE criteria) 1
cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*