CVE-2026-62239

MEDIUMPre-NVD 6.66.6
EchelonGraph scoreMEDIUM confidence

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

Score 6.6 from GitHub Security Advisory published 2026-07-14. A secondary CVSS source baseline 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
6.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.6Exploit: No code on recordExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

FlashAttention through 2.8.3.post1, fixed in commit 0816ef1, contains a symlink attack vulnerability in the download_and_copy() function within hopper/setup.py that extracts NVIDIA toolchain archives without validating symlinks or filtering tar members. A local attacker can pre-plant a symlink in the predictable cache directory to redirect extracted binaries to an attacker-chosen location, enabling arbitrary file write with victim privileges during build time.

CVSS v3
6.6
EG Score
6.6MEDIUMmedium confidence
EG Risk
46
EG Risk 46/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)
Severity66% × 45%
The EG Score, 6.6 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

July 13, 2026

Last Modified

September 17, 2026

Advisory Details (4)

Auto-updated Jul 13, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
Web page

FlashAttention Symlink Attack via tarfile.extractall in hopper/setup.py | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flashattention-symlink-attack-via-tarfile-extractall-in-hopper-setup-py
GitHub commit

commit 0816ef12f424 (Dao-AILab/flash-attention)

Fix landed in Dao-AILab/flash-attention commit 0816ef12f424 — awaiting tagged release

https://github.com/Dao-AILab/flash-attention/commit/0816ef12f424c6ec94b057a72c275b14f6e6edb2
GitHub pull request

hopper/setup.py: harden tarfile extraction against path traversal and symlink escape

Fix merged in Dao-AILab/flash-attention PR #2702 on 2026-07-12 — awaiting tagged release

https://github.com/Dao-AILab/flash-attention/pull/2702
Web page

Bare tarfile.extractall into Predictable Cache During Build in flash-attention · Issue #2637 · Dao-AILab/flash-attention · GitHub

https://github.com/Dao-AILab/flash-attention/issues/2637

Vendor Advisories for CVE-2026-62239(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 11× in last 7d / 36× 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 175 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 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-62239?
CVE-2026-62239 is a medium-severity vulnerability; its CVE record was published on July 13, 2026. FlashAttention through 2.8.3.post1, fixed in commit 0816ef1, contains a symlink attack vulnerability in the downloadandcopy() function within hopper/setup.py that extracts NVIDIA toolchain archives without validating symlinks or filtering tar members. A local attacker can pre-plant a symlink in the…
When was CVE-2026-62239 made public?
CVE-2026-62239 was made public on June 9, 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 July 13, 2026. EchelonGraph's copy of the record carries a last-modified date of September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-62239 actively exploited?
CVE-2026-62239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62239?
CVE-2026-62239 has a CVSS base score of 6.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62239?
An upstream fix for CVE-2026-62239 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-62239 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62239

Explore →

Is Your Infrastructure Affected by CVE-2026-62239?

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