CVE-2026-81683

openssl_encrypt before 1.4.9 Plaintext Private Key Storage

Published Aug 27, 2026 CVSS 4.0 · 8.6 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability in the openssl_encrypt Python package stores an mTLS client private key in plaintext within a world‑readable file when using package versions 1.4.8 and earlier. A local attacker who can read the device's file system may retrieve the private key, potentially compromising all communications protected by that key. This flaw is a classic case of improper data storage, mapped to CWE‑312.

Affected Systems

It affects the jahlives openssl_encrypt package, versions 1.4.8 and earlier, and can be mitigated by installing version 1.4.9 or later, which writes the key to a private 0600 file and only keeps the file path in SharedPreferences.

Risk and Exploitability

The CVSS score of 8.6 indicates high severity, and although an EPSS score is unavailable, the weakness remains significant for users who store keys locally without proper file permissions. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires legitimate file system access on the target device, making it a local‑but‑not‑remote attack. As the fix creates a dedicated private file and cleans previous cleartext entries, users should promptly upgrade, especially if the package remains at an older version.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest package release (v1.4.9 or newer).
  • Remove or zero‑out the old world‑readable SharedPreferences file that stored the key in cleartext.
  • Ensure that all key material is written to private 0600 files and that no sensitive data remains in world‑readable storage.

Generated by OpenCVE AI on August 27, 2026 at 18:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*
Type Values Removed Values Added
First Time appeared Jahlives
Jahlives openssl Encrypt
Vendors & Products Jahlives
Jahlives openssl Encrypt
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title openssl_encrypt before 1.4.9 Plaintext Private Key Storage
Weaknesses CWE-312
References
Metrics cvssV3_1

{'score': 8.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.6, 'vector': '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'}

Weaknesses
  • CWE-312

    Cleartext Storage of Sensitive Information

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 1, 2026, 3:21 PM
Reserved
Aug 27, 2026, 11:11 AM
Status
Analyzed
Published
Aug 27, 2026, 5:20 PM
Modified
Sep 2, 2026, 1:12 PM