Ciphertext weakening via CWD-relative KDF configuration
Published Aug 27, 2026 · Updated Aug 27, 2026
KDF downgrade in OpenSSL Encrypt 1.4.8 and earlier allows local users to weaken GUI-created ciphertext via a planted configuration file. crypt_settings.py reassigns CONFIG_FILE from the absolute per-user path to crypt_settings.json, causing SettingsTab to trust KDF values in the launch directory. Exploitation requires the legacy Tk GUI to launch from an attacker-writable directory; planted settings can reduce derivation to roughly one hash round and enable offline password brute force.
Summary
What happened
KDF downgrade in OpenSSL Encrypt 1.4.8 and earlier allows local users to weaken GUI-created ciphertext via a planted configuration file. crypt_settings.py reassigns CONFIG_FILE from the absolute per-user path to crypt_settings.json, causing SettingsTab to trust KDF values in the launch directory. Exploitation requires the legacy Tk GUI to launch from an attacker-writable directory; planted settings can reduce derivation to roughly one hash round and enable offline password brute force.
The record
- CVE
- CVE-2026-81697
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-426, T1565.001
- Attack vector
- local
- 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?
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.
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