CVE-2026-81683: high-severity vulnerability in jahlives openssl_encrypt
openssl_encrypt before 1.4.9 Plaintext Private Key Storage
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.6epss 0.1%
openssl_encrypt (pip package openssl-encrypt) versions 1.4.8 and earlier store an mTLS client private key in cleartext within a world-readable (0644) SharedPreferences file via the desktop GUI's Settings screen 'combined certificate and private key' PEM field. A local attacker with file system access can read the exposed private key. Version 1.4.9 writes the PEM to a dedicated 0600 file, keeps only its path in SharedPreferences, and migrates/scrubs existing cleartext values.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
jahlives · openssl_encryptRelated CVEs — jahlives openssl_encrypt
In the same product, most dangerous first.
CVE-2026-74899CRITICALopenssl_encrypt before 1.4.0 Sandbox Escape via Type HierarchyEPSS 0.8%CVE-2026-74878CRITICALopenssl_encrypt before 1.4.0 TOTP Rate Limiter BypassEPSS 0.7%CVE-2026-81690HIGHverify-usb before 1.4.9 Symlink Directory Traversal Code ExecutionEPSS 0.7%CVE-2026-74886CRITICALopenssl_encrypt before 1.4.0 Plugin Import Guard BypassEPSS 0.7%CVE-2026-74895CRITICALopenssl_encrypt before 1.4.0 Plugin Sandbox Bypass via Process IsolationEPSS 0.7%CVE-2026-74872CRITICALopenssl_encrypt before 1.4.0 Arbitrary Code Execution via WhirlpoolEPSS 0.7%