# OpenBao leaks HTTPRawBody in Audit Logs

Advisory record · `GHSA-ghfh-fmx4-26h8`

- **Identifiers:** `GHSA-ghfh-fmx4-26h8` · `BIT-openbao-2025-62513` · `CVE-2025-62513` · `GO-2025-4049`
- **State:** Confirmed
- **Severity:** CVSS 5.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-532](https://cwe.mitre.org/data/definitions/532.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 22 Oct 2025
- **Updated:** 27 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Oct 2025, 19:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/openbao/openbao` (Go): affected `>=0.0.0-20241114205727-b1235e585db7, <0.0.0-20251022165510-cc2c476bac66`; fixed in `0.0.0-20251022165510-cc2c476bac66`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> OpenBao (github.com/openbao/openbao) versions from 0.0.0-20241114205727-b1235e585db7 before 0.0.0-20251022165510-cc2c476bac66 have an audit log regression where raw HTTP bodies for a few endpoints were not redacted. Audit logs can then expose PKI ACME verification challenge codes and OIDC issuer auth and token response codes and claims, and third-party plugins may also be affected. Upgrade to 0.0.0-20251022165510-cc2c476bac66 or later, which fixes the issue. Deployments that do not use ACME or the OIDC issuer are not affected.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.7 Medium, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0032, the 24th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:56 UTC: First seen by agentprime
- 31 Oct 2026, 14:56 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-ghfh-fmx4-26h8)

## Sources

- [GitHub Advisory Database: GHSA-ghfh-fmx4-26h8](https://github.com/advisories/GHSA-ghfh-fmx4-26h8)
- [OSV: GHSA-ghfh-fmx4-26h8](https://osv.dev/vulnerability/GHSA-ghfh-fmx4-26h8)
- <https://github.com/openbao/openbao/security/advisories/GHSA-ghfh-fmx4-26h8>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-62513>
- <https://github.com/openbao/openbao/commit/cc2c476bac66e1d94776c2629793daec3af625f8>
- <https://github.com/openbao/openbao>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-ghfh-fmx4-26h8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ghfh-fmx4-26h8/>. Everything for agents: <https://agentprime.io/llms.txt>.
