Secret disclosure via recreated template runner stdout
Published Sep 23, 2026 · Updated Sep 23, 2026
Information disclosure in OpenBao Agent before 2.6.0 allows local users to read rendered secrets from standard output after rendering failures. In command/agent/exec/exec.go, a recreated template runner retains its default output stream instead of discarding dry-mode render output. The issue requires exec rendering with env_template, repeated failures through num_retries, and access to the Agent's standard output.
Summary
What happened
Information disclosure in OpenBao Agent before 2.6.0 allows local users to read rendered secrets from standard output after rendering failures. In command/agent/exec/exec.go, a recreated template runner retains its default output stream instead of discarding dry-mode render output. The issue requires exec rendering with env_template, repeated failures through num_retries, and access to the Agent's standard output.
The record
- CVE
- CVE-2026-77285
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- OpenBao
- Product
- OpenBao
- Classifications
- T1552
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started