CVE & CISA-KEV Catalog

CVE-2026-81681

MEDIUM
4.6
CVSS v3
NVD

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.

How to fix

Remediation Available
openssl encryptNVD
Affected:< 1.4.9Fixed in:1.4.9CVE-2026-81681derived from NVD

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorPhysical
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityNone
AvailabilityNone

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploit Intelligence

0.13%probability of exploitation in 30 days
3rdpercentile

Low risk: more likely to be exploited than 3% of all known CVEs.

References

Vendor Advisory1
Third-Party Advisory1

Related Vulnerabilities

Other CWE-311 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2026-34486High7.599%KEVFix
CVE-2026-27944Critical9.822%-Fix
CVE-2019-11367Critical9.82.8%-Fix
CVE-2017-8221High7.52.7%--
CVE-2018-10698Critical9.82.3%--
CVE-2016-10593High8.12.3%--

Common questions

How do I fix CVE-2026-81681?

Upgrade openssl encrypt to 1.4.9 or later.

Is CVE-2026-81681 being actively exploited?

Not that we know of. CVE-2026-81681 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.13% is the estimated probability that it will be exploited in the next 30 days. That is higher than 3% of all scored CVEs.

How severe is CVE-2026-81681?

CVE-2026-81681 has a CVSS v3 base score of 4.6, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-81681 affect?

Published advisories record a fix for openssl encrypt (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-81681
CVE-2026-81681 severity badge

Markdown

[![CVE-2026-81681](https://tridentstack.com/cve/badge/CVE-2026-81681.svg)](https://tridentstack.com/cve/CVE-2026-81681)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-81681"><img src="https://tridentstack.com/cve/badge/CVE-2026-81681.svg" alt="CVE-2026-81681"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Scan your fleet freeStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-02.