CVE-2026-66007

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-48613 (ENISA EUVD) · GHSA-379c-qx7v-6h59 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.5%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.5%
EPSS %ILE
46th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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.

The score's inputs: 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

July 24, 2026

Last Modified

October 24, 2026

Advisory Details (4)

Auto-updated Jul 24, 2026
Patch available. Sources: github_pr, github_commit.
Web page

Datasets Path Traversal via Unsanitized file_name Metadata | Advisories | VulnCheck

https://www.vulncheck.com/advisories/datasets-path-traversal-via-unsanitized-file-name-metadata
GitHub pull request

Fix 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/8325
Web page

Path 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/8324
GitHub commit

commit f989ef9b4cc6 (huggingface/datasets)

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

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17925631272026-10-21redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17918163162026-10-21redhat
redhatrhoai/odh-training-rocm64-torch29-py312-rhel9:17918094022026-10-19redhat
redhatrhaii/vllm-spyre-rhel9:17918183572026-10-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
datasets0.0.9 ... 5.0.0 (118 versions)
  • every version up to 5.0.1: fixed in 5.0.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 42× 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 217 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 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-66007?
CVE-2026-66007 is a medium-severity vulnerability; its CVE record was published on July 24, 2026. 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…
When was CVE-2026-66007 made public?
CVE-2026-66007 was made public on July 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 July 24, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-66007 actively exploited?
CVE-2026-66007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66007?
CVE-2026-66007 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-66007?
A fix for CVE-2026-66007 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-66007 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-66007

Explore →

Is Your Infrastructure Affected by CVE-2026-66007?

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