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).
CVE-2026-81690
Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity73% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 27, 2026verify-usb before 1.4.9 Symlink Directory Traversal Code Execution | Advisories | VulnCheck
https://www.vulncheck.com/advisories/verify-usb-before-1.4.9-symlink-directory-traversal-code-executionverify-usb silently skips content under a planted directory symlink, allowing a forged PASSED · Advisory · jahlives/openssl_encrypt · GitHub
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-hw7h-wqf5-6crxVendor Advisories for CVE-2026-81690(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:45 UTCGHSA enrichment
- 2026-08-29 07:55 UTCEG score recompute
- 2026-08-29 07:55 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:03 UTCGHSA enrichment
- 2026-08-28 09:21 UTCGHSA enrichment
- 2026-08-27 20:27 UTCEG score recompute
- 2026-08-27 20:27 UTCGHSA enrichment
- 2026-08-27 20:18 UTCEG score recompute
- 2026-08-27 20:18 UTCGHSA enrichment
- 2026-08-27 17:25 UTCEG score recompute
- 2026-08-27 16:47 UTCEG score recompute
- 2026-08-27 16:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-81690?
When was CVE-2026-81690 disclosed?
Is CVE-2026-81690 actively exploited?
What is the CVSS score of CVE-2026-81690?
How do I remediate CVE-2026-81690?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81690
Is Your Infrastructure Affected by CVE-2026-81690?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.