How severe is CVE-2026-81681?

CVE-2026-81681 has a CVSS 3.x base score of 4.6, rated medium severity. It is exploitable over physical access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-81681 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-81681?

CVE-2026-81681 affects Jahlives Openssl Encrypt. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-81681?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-81681 published?

CVE-2026-81681 was published on 2026-08-27 and last updated on 2026-09-02.

CVE-2026-81681

CVE-2026-81681 is a medium-severity vulnerability in Jahlives Openssl Encrypt with a CVSS 3.x base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-311.

Key facts

Severity: Medium (CVSS 3.x base score 4.6)
CVSS v4: 9.3
EPSS exploit prediction: 0% (3rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-311
Affected product: Jahlives Openssl Encrypt
Published: 2026-08-27
Last modified: 2026-09-02

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.

Frequently asked questions

What is CVE-2026-81681?: 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.
How severe is CVE-2026-81681?: CVE-2026-81681 has a CVSS 3.x base score of 4.6, rated medium severity. It is exploitable over physical access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-81681 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-81681?: CVE-2026-81681 affects Jahlives Openssl Encrypt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-81681?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-81681 published?: CVE-2026-81681 was published on 2026-08-27 and last updated on 2026-09-02.

References

Affected products (1)

cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*

More vulnerabilities in Jahlives Openssl Encrypt

CVE-2026-81702 — Critical (CVSS 9.8): openssl_encrypt before 1.4.9 fails to re-derive and validate fingerprints when loading identities from identity.json,…
CVE-2026-81701 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.9 use a denylist to identify trusted built-in plugins, allowing unsigned plugins in…
CVE-2026-81700 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.9 contain a signature verification vulnerability in gpg_runner.verify_detached that…
CVE-2026-74901 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain an authentication bypass vulnerability in pqc.py where AES-GCM decryption…
CVE-2026-74900 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain a critical vulnerability in pqc.py where KEM decapsulation failures…
CVE-2026-74899 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain a sandbox escape vulnerability in IsolatedPluginExecutor that exposes…

All CVEs affecting Jahlives Openssl Encrypt →

Other CWE-311 (Missing Encryption of Sensitive Data) vulnerabilities

CVE-2023-6339 — Critical (CVSS 10.0): Google Nest WiFi Pro root code-execution & user-data compromise
CVE-2023-4420 — Critical (CVSS 9.8): A remote unprivileged attacker can intercept the communication via e.g. Man-In-The-Middle, due to the absence of…
CVE-2023-0750 — Critical (CVSS 9.8): Yellobrik PEC-1864 implements authentication checks via javascript in the frontend interface. When the device can be…
CVE-2020-15331 — Critical (CVSS 9.8): Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded OAUTH_SECRET_KEY in /opt/axess/etc/default/axess.
CVE-2019-3431 — Critical (CVSS 9.8): All versions up to V4.01.01.02 of ZTE ZXCLOUD GoldenData VAP product have encryption problems vulnerability. Attackers…
CVE-2019-12924 — Critical (CVSS 9.8): MailEnable Enterprise Premium 10.23 was vulnerable to XML External Entity Injection (XXE) attacks that could be…

Browse all CWE-311 (Missing Encryption of Sensitive Data) vulnerabilities →