Path Traversal in datasets (CVE-2026-66007)
Summary
Path traversal in datasets (CVE-2026-66007). Confidential information can be exposed externally. Mitigation: upgrade to 5.0.1 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-66007 has been found in datasets.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade datasets to 5.0.1 or later.
If unsure, ask your IT team or search "datasets CVE-2026-66007" on the vendor's site.
CVE-2026-66007 (datasets) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Patched: 5.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in datasets.
Check the vendor advisory for the affected versions of datasets.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 5.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'datasets' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'datasets' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
datasetsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade datasets to 5.0.1ステージング環境で 5.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch vulncheck.com
- report github.com
- web github.com