CVE-2026-81690

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. The CNA's CVSS baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

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 (value × EchelonGraph’s weight)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

October 1, 2026

Advisory Details (2)

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

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 advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
openssl-encrypt0.2.2 ... 1.4.8 (53 versions)
  • every version up to 1.4.9: fixed in 1.4.9
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 103× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 173 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 73 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-10-13 06:17 UTCEG score recompute
  3. 2026-10-13 06:16 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-12 14:56 UTCEG score recompute
  6. 2026-10-11 19:20 UTCEG score recompute
  7. 2026-10-11 16:36 UTCEG score recompute
  8. 2026-10-11 13:54 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-10 15:12 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  12. 2026-10-10 01:55 UTCEG score recompute
  13. 2026-10-10 01:55 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-09 03:07 UTCEG score recompute
  16. 2026-10-09 03:07 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-10-08 01:20 UTCEG score recompute
  19. 2026-10-08 01:20 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-10-07 02:35 UTCEG score recompute
  22. 2026-10-07 02:35 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-06 13:46 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  25. 2026-10-06 00:54 UTCEG score recompute
Show 75 more
  1. 2026-10-06 00:54 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  2. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-10-05 08:28 UTCEG score recompute
  4. 2026-10-05 08:28 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  5. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-04 19:39 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  7. 2026-10-04 04:02 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  8. 2026-10-03 15:13 UTCEG score recompute
  9. 2026-10-03 15:13 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  10. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-02 19:08 UTCEG score recompute
  12. 2026-10-02 19:08 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  13. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-02 06:19 UTCEG score recompute
  15. 2026-10-02 06:19 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-01 15:28 UTCEG score recompute
  18. 2026-10-01 15:28 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  19. 2026-10-01 08:43 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  20. 2026-09-30 19:55 UTCEG score recompute
  21. 2026-09-30 19:55 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  22. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-09-30 05:01 UTCEG score recompute
  24. 2026-09-30 05:01 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  25. 2026-09-29 12:16 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  26. 2026-09-28 22:03 UTCEG score recompute
  27. 2026-09-28 22:02 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  28. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-09-28 09:13 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  30. 2026-09-27 20:24 UTCEG score recompute
  31. 2026-09-27 20:24 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-09-27 07:35 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  34. 2026-09-26 18:44 UTCEG score recompute
  35. 2026-09-26 18:44 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-09-25 17:03 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  38. 2026-09-25 04:14 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  39. 2026-09-24 15:24 UTCEG score recompute
  40. 2026-09-24 15:24 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  41. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-09-24 02:13 UTCEG score recompute
  43. 2026-09-24 02:13 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  45. 2026-09-23 13:24 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  46. 2026-09-23 00:28 UTCEG score recompute
  47. 2026-09-23 00:28 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  48. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  49. 2026-09-22 11:38 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  50. 2026-09-21 22:48 UTCEG score recompute
  51. 2026-09-21 22:48 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  52. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  53. 2026-09-21 09:58 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  54. 2026-09-20 21:09 UTCEG score recompute
  55. 2026-09-20 21:09 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  56. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  57. 2026-09-20 08:20 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  58. 2026-09-19 18:04 UTCEG score recompute
  59. 2026-09-19 18:04 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  60. 2026-09-19 05:12 UTCEG score recompute
  61. 2026-09-19 05:12 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  62. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  63. 2026-09-18 16:21 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  64. 2026-09-18 03:22 UTCEG score recompute
  65. 2026-09-18 03:22 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  66. 2026-09-17 14:33 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  67. 2026-09-17 01:41 UTCEG score recompute
  68. 2026-09-17 01:41 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  69. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  70. 2026-09-16 12:52 UTCEG score recompute
  71. 2026-09-16 12:52 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  72. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  73. 2026-09-16 00:03 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3
  74. 2026-09-15 11:14 UTCEG score recompute
  75. 2026-09-15 11:14 UTCGHSA enrichmentGHSA-vcf6-hg34-vx9w · GitHub severity HIGH · GitHub CVSS 7.3

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-81690?
CVE-2026-81690 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-81690 was made public on August 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 1, 2026; the record at its source may have been updated since.
Is CVE-2026-81690 actively exploited?
CVE-2026-81690 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81690?
CVE-2026-81690 has a CVSS base score of 7.3 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-81690?
A fix for CVE-2026-81690 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81690 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs