# OpenBao Agent Writes Secrets to Stdout

Advisory record · `GHSA-444v-8vxr-p36h`

- **Identifiers:** `GHSA-444v-8vxr-p36h` · `BIT-openbao-2026-77285` · `CVE-2026-77285` · `GO-2026-6554`
- **State:** Confirmed
- **Severity:** CVSS 2.4 Low
- **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 Sept 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Sept 2026, 20:36 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-20260714163218-90272575e5f5 || >=0.1.0, <=1.1.5`; fixed in `0.0.0-20260714163218-90272575e5f5`

## Machine-written summary

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

> OpenBao (Go module github.com/openbao/openbao) versions from 0.1.0 through 1.1.5, plus certain pseudo-version builds, are affected. When OpenBao Agent's exec rendering mode hits certain error conditions, typically after num_retries is reached, it writes secrets listed in env_template to stdout. The source does not say what local or remote access is needed to read that output. The fix is in pseudo-version 0.0.0-20260714163218-90272575e5f5, and the advisory also names OpenBao v2.6.0 as the patched release, so upgrade to one of those.

Written 1 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

- 2.4 Low, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:12 UTC: First seen by agentprime
- 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-444v-8vxr-p36h)

## Sources

- [GitHub Advisory Database: GHSA-444v-8vxr-p36h](https://github.com/advisories/GHSA-444v-8vxr-p36h)
- [OSV: GHSA-444v-8vxr-p36h](https://osv.dev/vulnerability/GHSA-444v-8vxr-p36h)
- <https://github.com/openbao/openbao/security/advisories/GHSA-444v-8vxr-p36h>
- <https://github.com/openbao/openbao/pull/3494>
- <https://github.com/openbao/openbao/pull/3495>
- <https://github.com/openbao/openbao/commit/90272575e5f58b3883fbb0ccb2238e9285722d1a>
- <https://github.com/openbao/openbao/commit/ee3aa4aff72c5176cf02af21eac7158899080878>
- <https://github.com/openbao/openbao>
- <https://github.com/openbao/openbao/releases/tag/v2.6.0>

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-444v-8vxr-p36h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-444v-8vxr-p36h/>. Everything for agents: <https://agentprime.io/llms.txt>.