CVE-2025-62513 json
OpenBao leaks HTTPRawBody in Audit Logs
published 2025-10-22 12 mo ago modified 2026-10-19 21 d ago also BIT-openbao-2025-62513 , EUVD-2025-35626 , GHSA-ghfh-fmx4-26h8 , GO-2025-4049
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/openbao/openbao 0.0.0-20251022165510-cc2c476bac66
- bitnami openbao 2.4.2
- openbao openbao 2.4.2
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20251105T184115-1.1
- openbao openSUSE Tumbleweed 2.4.3-1.1
opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15710-1openSUSE-SU-2025:15663-1
- openbao Alpine 3.24, Alpine 3.23, Alpine 3.22 2.4.3-r0
alpine advisories ALPINE-CVE-2025-62513
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-62513 updated cvss 4.5
github.com/openbao/openbao/audit: OpenBao leaks HTTPRawBody in Audit Logs
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.7 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 5.7 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/openbao/openbao | >=0.0.0-20241114205727-b1235e585db7, <0.0.0-20251022165510-cc2c476bac66 |
0.0.0-20251022165510-cc2c476bac66 |
| bitnami | openbao | >=2.2.0, <2.4.2 |
2.4.2 |
Affected products
- openbao openbao
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
-
github.com
/openbao/openbao/commit/cc2c476bac66e1d94776c2629793daec3af625f8
web, patch
-
github.com
/openbao/openbao/security/advisories/GHSA-ghfh-fmx4-26h8
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-62513
advisory, web
-
github.com
/openbao/openbao
package
Sources
- CVE List CVE-2025-62513
- GitHub Advisory GHSA-ghfh-fmx4-26h8
- NVD CVE-2025-62513
- OSV BIT-openbao-2025-62513
- OSV GO-2025-4049
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.