Datasets through 5.0.0, fixed in commit f989ef9, contains a path traversal vulnerability in folder-based dataset builders where the file_name metadata field is not properly validated before being joined to the dataset directory. Attackers can supply crafted file_name values with directory traversal sequences to read arbitrary local files, which are then embedded into output when save_to_disk or push_to_hub is called.
CVE-2026-66007
Score 6.5 from GitHub Security Advisory published 2026-07-24. a secondary CVSS source baseline 6.5; 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.5
- EG Score
- 6.5(medium)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 44%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
August 17, 2026
Advisory Details (4)
Auto-updated Jul 24, 2026Datasets Path Traversal via Unsanitized file_name Metadata | Advisories | VulnCheck
https://www.vulncheck.com/advisories/datasets-path-traversal-via-unsanitized-file-name-metadataFix path traversal via metadata file_name in folder-based builders
Fix merged in huggingface/datasets PR #8325 on 2026-07-23 — awaiting tagged release
https://github.com/huggingface/datasets/pull/8325Path traversal / arbitrary file read via the `file_name` metadata field in `*folder` dataset builders (no `trust_remote_code`) · Issue #8324 · huggingface/datasets · GitHub
https://github.com/huggingface/datasets/issues/8324commit f989ef9b4cc6 (huggingface/datasets)
Fix landed in huggingface/datasets commit f989ef9b4cc6 — awaiting tagged release
https://github.com/huggingface/datasets/commit/f989ef9b4cc6c0039a7a82458eebca49e2b58b4bVendor Advisories for CVE-2026-66007(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| datasets | 0.0.9 ... 5.0.0 (118 versions) | 5.0.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 88× 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.
Showing the most recent 100 of 101 total refreshes for this CVE.
- 2026-08-27 03:28 UTCEG score recompute
- 2026-08-27 03:28 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 05:39 UTCEG score recompute
- 2026-08-26 05:39 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 07:19 UTCEG score recompute
- 2026-08-25 07:19 UTCGHSA enrichment
- 2026-08-24 09:29 UTCEG score recompute
- 2026-08-24 09:29 UTCGHSA enrichment
- 2026-08-23 11:40 UTCEG score recompute
- 2026-08-23 11:40 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 13:52 UTCEG score recompute
- 2026-08-22 13:52 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 16:04 UTCEG score recompute
- 2026-08-21 16:04 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 18:15 UTCGHSA enrichment
- 2026-08-19 20:27 UTCEG score recompute
- 2026-08-19 20:27 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 18:54 UTCEG score recompute
- 2026-08-18 18:54 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 19:29 UTCEG score recompute
- 2026-08-17 19:29 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 03:17 UTCEG score recompute
- 2026-08-17 03:17 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:29 UTCEG score recompute
- 2026-08-16 05:29 UTCGHSA enrichment
- 2026-08-15 07:41 UTCEG score recompute
- 2026-08-15 07:41 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 09:53 UTCEG score recompute
- 2026-08-14 09:53 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:04 UTCGHSA enrichment
- 2026-08-12 14:16 UTCEG score recompute
- 2026-08-12 14:16 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 16:27 UTCEG score recompute
- 2026-08-11 16:27 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 18:39 UTCGHSA enrichment
- 2026-08-09 20:51 UTCEG score recompute
- 2026-08-09 20:51 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-08 23:03 UTCEG score recompute
- 2026-08-08 23:03 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 01:14 UTCEG score recompute
- 2026-08-08 01:14 UTCGHSA enrichment
- 2026-08-07 03:26 UTCEG score recompute
- 2026-08-07 03:26 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 05:38 UTCEG score recompute
- 2026-08-06 05:38 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 07:50 UTCEG score recompute
- 2026-08-05 07:50 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 09:57 UTCGHSA enrichment
- 2026-08-03 12:00 UTCEG score recompute
- 2026-08-03 12:00 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 14:11 UTCEG score recompute
- 2026-08-02 14:11 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 16:23 UTCEG score recompute
- 2026-08-01 16:23 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 18:34 UTCGHSA enrichment
- 2026-07-30 20:43 UTCEG score recompute
- 2026-07-30 20:43 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 16:23 UTCEG score recompute
- 2026-07-30 16:23 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 18:31 UTCGHSA enrichment
- 2026-07-28 20:39 UTCEG score recompute
- 2026-07-28 20:39 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 22:50 UTCEG score recompute
- 2026-07-27 22:49 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 00:49 UTCEG score recompute
- 2026-07-27 00:49 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:00 UTCEG score recompute
- 2026-07-26 02:59 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 15:13 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-66007?
When was CVE-2026-66007 disclosed?
Is CVE-2026-66007 actively exploited?
What is the CVSS score of CVE-2026-66007?
How do I remediate CVE-2026-66007?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-66007
Is Your Infrastructure Affected by CVE-2026-66007?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.