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.
CVE-2026-62239
Score 6.6 from GitHub Security Advisory published 2026-07-14. a secondary CVSS source baseline 6.6; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.6
- EG Score
- 6.6(high)
- EPSS
- 2.9%
- KEV
- Not listed
Published
July 13, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 13, 2026FlashAttention 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-pycommit 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/0816ef12f424c6ec94b057a72c275b14f6e6edb2hopper/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/2702Bare 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/2637Vendor 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 9× in last 7d / 9× 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-07-15 22:28 UTCEG score recompute
- 2026-07-15 22:28 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 21:55 UTCEG score recompute
- 2026-07-14 21:55 UTCGHSA enrichment
- 2026-07-13 21:23 UTCEG score recompute
- 2026-07-13 21:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-62239?
When was CVE-2026-62239 disclosed?
Is CVE-2026-62239 actively exploited?
What is the CVSS score of CVE-2026-62239?
How do I remediate CVE-2026-62239?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62239
Is Your Infrastructure Affected by CVE-2026-62239?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.