CVE-2026-81681 in openssl-encrypt
Summary
by MITRE • 08/27/2026
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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 08/27/2026
The vulnerability identified in versions of the openssl-encrypt Python package up through version 1.4.8 represents a critical failure in cryptographic implementation known as crypto-shaming or false security assurance. The software advertises its functionality by presenting a portable USB workspace that appears to be secured with AES-256-GCM encryption, a standard widely regarded for providing both confidentiality and integrity. Upon initialization, the application writes a specific marker file to indicate that the workspace is encrypted, thereby signaling to users and potential observers that data protection mechanisms are active. This branding creates a strong expectation of security, leading users to trust the system with sensitive information under the assumption that their files are protected against unauthorized access.
The technical flaw lies in the disconnect between the advertised cryptographic operations and the actual file system handling. While the application derives an encryption key from user credentials or other inputs, it fails to apply this derived key to encrypt the contents of the workspace directory. Instead, all data written by the user is stored directly on the removable media in cleartext format. The marker indicating encryption exists solely for display purposes and does not trigger any actual cryptographic transformation of the underlying files. This means that despite the software's claims, no confidentiality controls are enforced at the storage layer, rendering the AES-256-GCM implementation effectively non-existent for the stored data.
The operational impact of this vulnerability is severe due to its reliance on physical access by an attacker. Since the data remains unencrypted on the USB drive, any individual with physical possession of the media can mount it and read all files without needing to bypass encryption or crack keys. This scenario poses a significant risk for users who utilize portable drives for transporting sensitive documents, personal records, or proprietary business information across different environments. The presence of the encryption marker may lead to complacency, as users might neglect additional physical security measures such as locking devices in secure locations, assuming that digital encryption provides sufficient protection against theft or loss.
This vulnerability aligns with CWE-321, which describes the use of a single cryptographic primitive for multiple purposes where one purpose is not adequately protected, although more specifically it reflects CWE-798: Use of Hard-coded Credentials if we consider the key derivation failure as a form of improper credential handling, or more accurately CWE-650: Trusting Untrusted Inputs in combination with CWE-310: Cryptographic Issues. In terms of attack vectors, this falls under ATT&CK technique T1552.004, specifically Unsecured Credentials on Removable Media, as the sensitive data is exposed due to a lack of encryption at rest. The failure also relates to CWE-922: Insecure Storage of Sensitive Information, where the application fails to protect stored data through appropriate access controls or cryptographic mechanisms.
The issue was resolved in version 1.4.9 by implementing proper authenticated encryption for the workspace vault. The updated software ensures that all files written to the workspace are encrypted using AES-256-GCM before being persisted to disk, and it verifies integrity upon read operations. This correction eliminates the false sense of security and ensures that physical access to the media no longer grants immediate plaintext access to user data. Users relying on this package should immediately upgrade to version 1.4.9 or later to restore expected security guarantees. Additionally, organizations deploying such tools should conduct audits to ensure that cryptographic implementations match their advertised capabilities, as discrepancies between documentation and code behavior can lead to significant exposure of sensitive information even when strong algorithms are nominally selected.