CVE-2026-65010

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreHIGH confidence

Score 6.6 from GitHub Security Advisory published 2026-07-23. the CNA's CVSS baseline 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this weekElevated
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.6Exploit: Elevated riskExposed: 0

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

Datasets through 5.00, fixed in commit ad2d853, contains a symlink-following vulnerability in Extractor.extract() that allows local attackers to write arbitrary files by pre-planting symlinks at predictable output paths. Attackers can redirect archive extraction to arbitrary filesystem locations in shared-cache environments, enabling overwrite of sensitive files and potential privilege escalation or code execution.

CVSS v3
6.6
EG Score
6.6(high)
EG Risk
46(Track)
EG Risk 46/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
Severity66% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated Jul 24, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Datasets Symlink-following Arbitrary File Write via Extractor.extract() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/datasets-symlink-following-arbitrary-file-write-via-extractor-extract
github_pr

Fix symlink-following arbitrary file write in archive extraction

Fix merged in huggingface/datasets PR #8303 on 2026-07-06 — awaiting tagged release

https://github.com/huggingface/datasets/pull/8303
generic

[security] Symlink-Following Arbitrary File Write via Archive Extraction in huggingface/datasets · Issue #8296 · huggingface/datasets · GitHub

https://github.com/huggingface/datasets/issues/8296
github_commit

commit ad2d853ae2ce (huggingface/datasets)

Fix landed in huggingface/datasets commit ad2d853ae2ce — awaiting tagged release

https://github.com/huggingface/datasets/commit/ad2d853ae2ce41d8068c23b44c2e29004312ccee

Vendor Advisories for CVE-2026-65010(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 13× in last 7d / 13× 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-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 00:49 UTCEG score recompute
  3. 2026-07-27 00:49 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 03:07 UTCEG score recompute
  7. 2026-07-26 03:07 UTCGHSA enrichment
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-25 14:18 UTCEPSS rescore
  10. 2026-07-24 14:18 UTCEPSS rescore
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-23 18:22 UTCEG score recompute
  13. 2026-07-23 18:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65010?
CVE-2026-65010 is a medium vulnerability published on July 23, 2026. Datasets through 5.00, fixed in commit ad2d853, contains a symlink-following vulnerability in Extractor.extract() that allows local attackers to write arbitrary files by pre-planting symlinks at predictable output paths. Attackers can redirect archive extraction to arbitrary filesystem locations in…
When was CVE-2026-65010 disclosed?
CVE-2026-65010 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65010 actively exploited?
CVE-2026-65010 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 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-65010?
CVE-2026-65010 has a CVSS v4.0 base score of 6.6 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-65010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65010, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-65010?

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

Start Free Scan →Browse All CVEs