CVE-2026-81690

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).
Configurations

Configuration 1 (hide)

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

History

No history.

Information

Published : 2026-08-27 17:20

Updated : 2026-09-02 13:10


NVD link : CVE-2026-81690

Mitre link : CVE-2026-81690

CVE.ORG link : CVE-2026-81690


JSON object : View

Products Affected

jahlives

  • openssl_encrypt
CWE
CWE-59

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