CVE-2026-81681

openssl_encrypt before 1.4.9 False Encryption via Cleartext Storage

Published Aug 27, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8 advertise a portable USB workspace as an 'Encrypted USB Workspace' with AES-256-GCM encryption and write a marker declaring the workspace encrypted, but the workspace directory is actually stored in cleartext and the derived encryption key is never applied to it. A user who trusts the branding and places files in the workspace leaves them unencrypted on the removable media, so an attacker with physical access to the media can read the sensitive files. Fixed in 1.4.9, which seals the workspace into an authenticated AES-256-GCM vault.

Analysis

AI-generated

Technical impact

The openssl-encrypt package up to version 1.4.8 presents an "Encrypted USB Workspace" that is advertised as using AES‑256‑GCM encryption, yet it stores the workspace directory in cleartext and never applies the derived encryption key. Consequently, any files a user places in the workspace are written to removable media without cryptographic protection, exposing sensitive data to anyone who examines the storage medium.

Affected Systems

The vulnerability affects the jahlives:openssl_encrypt Python package (pip package openssl‑encrypt) for all releases through 1.4.8. Versions 1.4.9 and later include a fix that seals the workspace into an authenticated AES‑256‑GCM vault, preventing the storage of unencrypted data.

Risk and Exploitability

The CVSS score of 9.3 classifies this flaw as critical, and the EPSS score is not available. It is not listed in CISA’s KEV catalog. The attack requires physical possession of the removable media, after which an attacker can read the unencrypted files. The flaw is easily exploitable for users who trust the branding and are unaware that the data is not encrypted, leading to an unprivileged disclosure of confidential information.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade openssl‑encrypt to version 1.4.9 or later to ensure the workspace is stored in an authenticated AES‑256‑GCM vault.
  • If an upgrade is not immediately possible, disable or avoid using the "Encrypted USB Workspace" feature in older versions.
  • Manually encrypt any sensitive files before placing them on removable media or use an alternative encrypted storage solution.

Generated by OpenCVE AI on August 27, 2026 at 18:10 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': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8 advertise a portable USB workspace as an 'Encrypted USB Workspace' with AES-256-GCM encryption and write a marker declaring the workspace encrypted, but the workspace directory is actually stored in cleartext and the derived encryption key is never applied to it. A user who trusts the branding and places files in the workspace leaves them unencrypted on the removable media, so an attacker with physical access to the media can read the sensitive files. Fixed in 1.4.9, which seals the workspace into an authenticated AES-256-GCM vault.
Title openssl_encrypt before 1.4.9 False Encryption via Cleartext Storage
Weaknesses CWE-311
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-311

    Missing Encryption of Sensitive Data

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:13 PM