# CVE-2026-77285: OpenBao Agent Writes Secrets to Stdout

> OpenBao Agent may leak secrets to stdout during rendering failures, allowing local users or log collectors to read sensitive data.

- **Severity:** Low 2.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** BIT-openbao-2026-77285, GHSA-444v-8vxr-p36h, GO-2026-6554, MINI-2cc6-xjcm-hmqr, MINI-w3w8-2xch-cv4m

## What is CVE-2026-77285?

CVE-2026-77285 is a low-severity vulnerability in openbao, published on 23 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, OpenBao Agent's exec rendering mode could write secrets from env_template to standard output when command/agent/exec/exec.go re-created the template runner after repeated rendering failures, primarily after num_retries was reached. A process supervisor, log collector, or local user able to read that output could obtain the rendered secret values. This issue is fixed in version 2.6.0.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-77285?

6 open source packages ship an affected version, including github.com/openbao/openbao and openbao.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openbao/openbao` | Go | All versions | 0.0.0-20260714163218-90272575e5f5 |
| `github.com/openbao/openbao` | Go | All versions | 0.0.0-20260714163218-90272575e5f5 |
| `github.com/openbao/openbao` | Go | All versions | 0.0.0-20260714163218-90272575e5f5 |
| `github.com/openbao/openbao` | Go | From 0.1.0 to 1.1.5 | None |
| `github.com/openbao/openbao` | Go | From 0.1.0 to 1.1.5 | None |
| `openbao` | Bitnami | All versions | 2.6.0 |

## How do I fix CVE-2026-77285?

Upgrade github.com/openbao/openbao to 0.0.0-20260714163218-90272575e5f5 or later.

## Is CVE-2026-77285 being exploited?

There is no known exploitation of CVE-2026-77285 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77285 and fix it if it is affected.

What it is: CVE-2026-77285 is a low-severity vulnerability in openbao, published on 23 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-77285 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260714163218-90272575e5f5
- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260714163218-90272575e5f5
- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260714163218-90272575e5f5
- github.com/openbao/openbao (Go): affected from 0.1.0 up to 1.1.5; no fix listed
- github.com/openbao/openbao (Go): affected from 0.1.0 up to 1.1.5; no fix listed
- openbao (Bitnami): affected all versions; fixed in 2.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77285/ (Markdown: https://insights.sbomify.com/CVE-2026-77285/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77285
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77285
- OSV: https://osv.dev/vulnerability/CVE-2026-77285

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77285/
Summaries are generated and may contain mistakes; the official description above is the record.