CVE-2026-81681 openssl_encrypt before 1.4.9 False Encryption via Cleartext Storage

Critical 9.3 Published Updated

The library falsely claims to encrypt USB workspaces, leaving data in cleartext and allowing attackers with physical access to read sensitive files.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-81681?

CVE-2026-81681 is a critical vulnerability in Jahlives Openssl Encrypt, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-311

Which versions are affected by CVE-2026-81681?

1 open source package ship an affected version, including openssl-encrypt. It affects 1 product.

PackageAffectedFixed in
openssl-encrypt PyPIAll versions1.4.9

Products include Jahlives Openssl Encrypt.

How do I fix CVE-2026-81681?

Upgrade openssl-encrypt to 1.4.9 or later.

Is CVE-2026-81681 being exploited?

There is no known exploitation of CVE-2026-81681 in the wild and no public exploit code.

All Jahlives Openssl Encrypt vulnerabilities

Sources

Also known as GHSA-2jv6-qqfm-m46m, GHSA-c4f3-9gjw-6j6x, PYSEC-2026-3791.

Is CVE-2026-81681 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free