CVEPublished 2026-08-27Modified 2026-09-020 articles on news4 live referencesNVD data

CVE-2026-81681Jahlives · Openssl_encrypt

Vulnerability data via NVD (ingested)

CVSS v3.1
4.6
MEDIUM
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS percentile
3
Exploit Prediction Scoring System · top 97% of all CVEs
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.

Timeline
Published 2026-08-27
Modified 2026-09-02

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

More intel sources (5)

Known PoCs on GitHub

No public proof-of-concept repositories found for CVE-2026-81681 on GitHub.
We haven't classified any articles referencing CVE-2026-81681 yet. The external references above still apply.