Local mTLS key disclosure via world-readable preferences
Published Aug 27, 2026 · Updated Aug 27, 2026
Cleartext key storage in OpenSSL Encrypt 1.4.8 and earlier allows local users to read an mTLS client private key. The desktop GUI Settings screen saves the combined certificate and private key PEM value unencrypted in a 0644 SharedPreferences file. Local file-system access and prior use of that Settings field are required; exposure is limited to disclosure of the stored client key.
Summary
What happened
Cleartext key storage in OpenSSL Encrypt 1.4.8 and earlier allows local users to read an mTLS client private key. The desktop GUI Settings screen saves the combined certificate and private key PEM value unencrypted in a 0644 SharedPreferences file. Local file-system access and prior use of that Settings field are required; exposure is limited to disclosure of the stored client key.
The record
- CVE
- CVE-2026-81683
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-312, 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?
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.
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