Credential disclosure via unredacted debug argument
Published Aug 27, 2026 · Updated Aug 27, 2026
Information disclosure in OpenSSL Encrypt before 1.4.9 allows local users to obtain a keyserver bearer token from debug output. The sanitize_argv_for_debug function leaves the positional token after keyserver set-token unchanged when dumping sys.argv to stderr. Exposure requires --debug during token configuration, after which the credential can persist in captured logs or terminal history.
Summary
What happened
Information disclosure in OpenSSL Encrypt before 1.4.9 allows local users to obtain a keyserver bearer token from debug output. The sanitize_argv_for_debug function leaves the positional token after keyserver set-token unchanged when dumping sys.argv to stderr. Exposure requires --debug during token configuration, after which the credential can persist in captured logs or terminal history.
The record
- CVE
- CVE-2026-81715
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=0 <1.4.9
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo