Description
openssl-encrypt (pip package) before 1.4.9 contains a symlink-following flaw in its verify-usb v2 added-file allowlist scan. The scan enumerated the drive with rglob(), which in CPython does not descend into symlinked directories and treats the symlink as an ordinary directory, while O_NOFOLLOW on the hash side binds only the final path component. An evil-maid attacker with physical access to the removable drive could replace a tool-tree directory with a symlink to a copy containing byte-identical files plus a planted __pycache__/*.pyc file (which CPython loads in preference to recompiling the clean .py). The planted file is never enumerated, added_files stays 0, and verify-usb reports PASSED, resulting in code execution when the victim runs the portable install. Fixed in 1.4.9 (affects both 1.4.x and 1.5.x lines).
Published: 2026-08-27
Score: 8.7 High
EPSS: < 1% Very Low
KEV: No
Impact: Code Execution via Symlink Abuse
Action: Patch Immediately
AI Analysis

Impact

This vulnerability is a symlink following flaw in the openssl_encrypt Python package’s verify-usb component. The package’s file enumeration routine ignores symlinked directories, allowing an attacker with physical access to a removable drive to replace a legitimate directory with a symlink to a malicious copy that contains a pre‑compiled __pycache__/*.pyc file. CPython prioritizes compiled bytecode, so the malicious script is inadvertently imported while the scanner reports the check as passed. The result is arbitrary code execution when the user runs the portable installer. The weakness maps directly to CWE‑59, a path traversal / symlink vulnerability.

Affected Systems

The affected product is the openssl_encrypt package distributed via PyPI and maintained by jahlives. Versions prior to 1.4.9 – including the 1.4.x and 1.5.x lines – are impacted.

Risk and Exploitability

The CVSS score of 8.7 classifies this as a high‑severity flaw. EPSS data is not available, but the vulnerability is not listed in CISA’s KEV catalog. Exploitation requires physical access to the removable media and the subsequent execution of the portable installer. Once executed, an attacker can run arbitrary code with the privileges of the user running the installer. Although not exploitable over the network, the impact is significant for environments that routinely process user‑supplied USB media.

Generated by OpenCVE AI on August 27, 2026 at 18:03 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the openssl_encrypt package to version 1.4.9 or newer for all deployments.
  • Re‑install or refresh any existing installations of the package to ensure the patch is applied.
  • If immediate upgrade is not feasible, restrict physical access to removable drives that could be tampered and avoid running portable installers from untrusted media.

Generated by OpenCVE AI on August 27, 2026 at 18:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 02 Sep 2026 13:30:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*

Thu, 27 Aug 2026 18:00:00 +0000

Type Values Removed Values Added
First Time appeared Jahlives
Jahlives openssl Encrypt
Vendors & Products Jahlives
Jahlives openssl Encrypt

Thu, 27 Aug 2026 16:45:00 +0000

Type Values Removed Values Added
Description openssl-encrypt (pip package) before 1.4.9 contains a symlink-following flaw in its verify-usb v2 added-file allowlist scan. The scan enumerated the drive with rglob(), which in CPython does not descend into symlinked directories and treats the symlink as an ordinary directory, while O_NOFOLLOW on the hash side binds only the final path component. An evil-maid attacker with physical access to the removable drive could replace a tool-tree directory with a symlink to a copy containing byte-identical files plus a planted __pycache__/*.pyc file (which CPython loads in preference to recompiling the clean .py). The planted file is never enumerated, added_files stays 0, and verify-usb reports PASSED, resulting in code execution when the victim runs the portable install. Fixed in 1.4.9 (affects both 1.4.x and 1.5.x lines).
Title verify-usb before 1.4.9 Symlink Directory Traversal Code Execution
Weaknesses CWE-59
References
Metrics cvssV3_1

{'score': 7.3, 'vector': 'CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Jahlives Openssl Encrypt
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-27T19:25:48.938Z

Reserved: 2026-08-27T11:12:00.889Z

Link: CVE-2026-81690

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2026-08-27T17:20:58.843

Modified: 2026-09-02T13:10:16.537

Link: CVE-2026-81690

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-27T18:45:04Z

Weaknesses
  • CWE-59

    Improper Link Resolution Before File Access ('Link Following')