CVE-2026-81690

HIGHPre-NVD 7.37.3
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

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 computed
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

August 27, 2026

Last Modified

September 2, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
Patch available. Sources: github.
generic

verify-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-execution
github Patch Available

verify-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-6crx

Vendor 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.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
openssl-encrypt0.2.2 ... 1.4.8 (53 versions)1.4.9

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 89× 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.

  1. 2026-09-19 05:12 UTCEG score recompute
  2. 2026-09-19 05:12 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 16:21 UTCGHSA enrichment
  5. 2026-09-18 03:22 UTCEG score recompute
  6. 2026-09-18 03:22 UTCGHSA enrichment
  7. 2026-09-17 14:33 UTCGHSA enrichment
  8. 2026-09-17 01:41 UTCEG score recompute
  9. 2026-09-17 01:41 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 12:52 UTCEG score recompute
  12. 2026-09-16 12:52 UTCGHSA enrichment
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 00:03 UTCGHSA enrichment
  15. 2026-09-15 11:14 UTCEG score recompute
  16. 2026-09-15 11:14 UTCGHSA enrichment
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-14 22:25 UTCGHSA enrichment
  20. 2026-09-14 09:35 UTCGHSA enrichment
  21. 2026-09-13 20:46 UTCEG score recompute
  22. 2026-09-13 20:46 UTCGHSA enrichment
  23. 2026-09-13 07:56 UTCGHSA enrichment
  24. 2026-09-12 19:08 UTCEG score recompute
  25. 2026-09-12 19:08 UTCGHSA enrichment
Show 64 more
  1. 2026-09-12 06:18 UTCGHSA enrichment
  2. 2026-09-11 17:29 UTCEG score recompute
  3. 2026-09-11 17:29 UTCGHSA enrichment
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 04:25 UTCGHSA enrichment
  7. 2026-09-10 15:35 UTCEG score recompute
  8. 2026-09-10 15:35 UTCGHSA enrichment
  9. 2026-09-10 02:38 UTCGHSA enrichment
  10. 2026-09-09 13:49 UTCGHSA enrichment
  11. 2026-09-09 00:41 UTCEG score recompute
  12. 2026-09-09 00:41 UTCGHSA enrichment
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-08 11:23 UTCGHSA enrichment
  15. 2026-09-08 11:21 UTCGHSA enrichment
  16. 2026-09-07 21:36 UTCEG score recompute
  17. 2026-09-07 21:36 UTCGHSA enrichment
  18. 2026-09-07 08:47 UTCGHSA enrichment
  19. 2026-09-06 19:58 UTCEG score recompute
  20. 2026-09-06 19:58 UTCGHSA enrichment
  21. 2026-09-06 13:48 UTCEPSS rescore
  22. 2026-09-06 07:08 UTCGHSA enrichment
  23. 2026-09-05 18:18 UTCEG score recompute
  24. 2026-09-05 18:18 UTCGHSA enrichment
  25. 2026-09-05 15:31 UTCEPSS rescore
  26. 2026-09-05 05:28 UTCGHSA enrichment
  27. 2026-09-04 16:39 UTCEG score recompute
  28. 2026-09-04 16:38 UTCGHSA enrichment
  29. 2026-09-04 05:07 UTCEPSS rescore
  30. 2026-09-04 03:48 UTCGHSA enrichment
  31. 2026-09-03 14:57 UTCGHSA enrichment
  32. 2026-09-03 02:05 UTCEG score recompute
  33. 2026-09-03 02:05 UTCGHSA enrichment
  34. 2026-09-02 14:12 UTCEPSS rescore
  35. 2026-09-02 13:13 UTCGHSA enrichment
  36. 2026-09-02 01:43 UTCEG score recompute
  37. 2026-09-02 01:43 UTCGHSA enrichment
  38. 2026-09-01 13:54 UTCEPSS rescore
  39. 2026-09-01 12:54 UTCEG score recompute
  40. 2026-09-01 12:53 UTCGHSA enrichment
  41. 2026-09-01 04:40 UTCEPSS rescore
  42. 2026-09-01 04:40 UTCEPSS rescore
  43. 2026-09-01 00:05 UTCGHSA enrichment
  44. 2026-08-31 11:14 UTCGHSA enrichment
  45. 2026-08-30 22:24 UTCEG score recompute
  46. 2026-08-30 22:24 UTCGHSA enrichment
  47. 2026-08-30 19:18 UTCEPSS rescore
  48. 2026-08-30 19:17 UTCEPSS rescore
  49. 2026-08-30 09:35 UTCEG score recompute
  50. 2026-08-30 09:35 UTCGHSA enrichment
  51. 2026-08-30 01:22 UTCEPSS rescore
  52. 2026-08-29 20:45 UTCGHSA enrichment
  53. 2026-08-29 07:55 UTCEG score recompute
  54. 2026-08-29 07:55 UTCGHSA enrichment
  55. 2026-08-28 21:42 UTCEPSS rescore
  56. 2026-08-28 19:03 UTCGHSA enrichment
  57. 2026-08-28 09:21 UTCGHSA enrichment
  58. 2026-08-27 20:27 UTCEG score recompute
  59. 2026-08-27 20:27 UTCGHSA enrichment
  60. 2026-08-27 20:18 UTCEG score recompute
  61. 2026-08-27 20:18 UTCGHSA enrichment
  62. 2026-08-27 17:25 UTCEG score recompute
  63. 2026-08-27 16:47 UTCEG score recompute
  64. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81690?
CVE-2026-81690 is a high vulnerability published on August 27, 2026. 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 ONOFOLLOW on…
When was CVE-2026-81690 disclosed?
CVE-2026-81690 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81690 actively exploited?
CVE-2026-81690 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.0% of all scored CVEs.
What is the CVSS score of CVE-2026-81690?
CVE-2026-81690 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-81690?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81690, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-81690

Explore →

Is Your Infrastructure Affected by CVE-2026-81690?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.