GHSA-444v-8vxr-p36h BIT-openbao-2026-77285 CVE-2026-77285 GO-2026-6554

OpenBao Agent Writes Secrets to Stdout

Low Go

Severity: 0.0 / 10; Low · CVSS 4.0
Exploit chance (EPSS): 0.17%; Chance of exploitation in the next 30 days. Higher than 5.68% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-532 Insertion of Sensitive Information into Log File
Fix: 0.0.0-20260714163218-90272575e5f5; Upgrade github.com/openbao/openbao to this version or later

Description

Impact

During certain error conditions, OpenBao Agent's exec rendering mode will incorrectly write secrets specified in env_template to stdout. This primarily happens when num_retries is met.

This vulnerability is original to Vault and was reported via the OpenBao security mailing list.

Patches

This is addressed in OpenBao v2.6.0 GA.

Affected versions

Go

Package	Vulnerable	Fixed in
github.com/openbao/openbao	`< 0.0.0-20260714163218-90272575e5f5`	`0.0.0-20260714163218-90272575e5f5`
github.com/openbao/openbao	`>= 0.1.0, <= 1.1.5`	No fix yet
github.com/openbao/openbao	`< 0.0.0-20260714163218-90272575e5f5` `>= 0.1.0`	`0.0.0-20260714163218-90272575e5f5`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/openbao/openbao Go → `0.0.0-20260714163218-90272575e5f5`

go

go get github.com/openbao/openbao@v0.0.0-20260714163218-90272575e5f5 && go mod tidy

Severity breakdown

CVSS 4.0 0.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

Attack vector: Local
Attack complexity: Low
Attack requirements: Present
Privileges required: High
User interaction: Active
Confidentiality (vulnerable system): Low
Integrity (vulnerable system): None
Availability (vulnerable system): None
Confidentiality (subsequent systems): High
Integrity (subsequent systems): High
Availability (subsequent systems): High

Weakness

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it

Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution: Remove debug log files before deploying the application into production.
Operation: Protect log files against unauthorized read/write.
Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Packages

github.com/openbao/openbao

Timeline

Sep 22, 2026 Published
Oct 1, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-xp3c-3jw3-4vcr OpenBao Skips Stricter Deny Policy for LIST operations	Medium	Also affects github.com/openbao/openbao
GHSA-34fc-gh42-pj53 OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack	Critical	Also affects github.com/openbao/openbao
GHSA-59w7-v8rr-pr4p OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters	High	Also affects github.com/openbao/openbao
GHSA-8w8f-r2xv-4q4j OpenBao: Transit secrets engine crashes on key creation with `derived: true` for asymmetric key types	Medium	Also affects github.com/openbao/openbao
GHSA-mwr2-wmgp-crj6 OpenBao's System Backend allows Unauthorized Management of the containing Namespace	Low	Also affects github.com/openbao/openbao
GHSA-c36x-h252-g9x2 OpenBao: Cross-namespace lease revocation/renewal via canonical sys/leases/{revoke,renew} — incomplete fix of CVE-2026-45808	Low	Also affects github.com/openbao/openbao
GHSA-6mwx-4547-5vc9 OpenBao: LDAPi ldaputil (wrong escape func)	Medium	Also affects github.com/openbao/openbao
GHSA-7j6w-vvw2-5f9c OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens	Medium	Also affects github.com/openbao/openbao

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor