Plaintext confirmation via cleartext unkeyed SHA-256 hash
Published Aug 27, 2026 · Updated Aug 27, 2026
Information disclosure in jahlives OpenSSL Encrypt before 1.4.9 allows attackers to confirm plaintext guesses from encrypted files. The file writer places hashes.original_hash, an unkeyed SHA-256 digest of the plaintext, in cleartext header metadata readable without the password. Possession of an affected encrypted file is sufficient to test candidate plaintexts offline or correlate identical plaintexts across separately encrypted files.
Summary
What happened
Information disclosure in jahlives OpenSSL Encrypt before 1.4.9 allows attackers to confirm plaintext guesses from encrypted files. The file writer places hashes.original_hash, an unkeyed SHA-256 digest of the plaintext, in cleartext header metadata readable without the password. Possession of an affected encrypted file is sufficient to test candidate plaintexts offline or correlate identical plaintexts across separately encrypted files.
The record
- CVE
- CVE-2026-81688
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-311
- Attack vector
- network
- Privileges
- unauthenticated
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