How severe is CVE-2026-66007?

No CVSS score has been assigned to CVE-2026-66007 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-66007?

CVE-2026-66007 affects the following packages: datasets (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-66007?

Update datasets to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-66007 is resolved across your whole dependency graph.

How do I detect CVE-2026-66007 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasets, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-66007 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-66007 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-66007 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-66007?

CVE-2026-66007 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-66007?

CVE-2026-66007 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-66007 published, and has it been updated?

CVE-2026-66007 was published on July 24, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-66007 — datasets

Fix: huggingface/datasets@f989ef9

CVE-2026-66007 is a Path Traversal vulnerability in datasets. A fix is available for datasets — see the affected versions and patch details below.

Datasets Path Traversal via Unsanitized file_name Metadata

Also known asGHSA-379c-qx7v-6h59PYSEC-2026-3716

Published

Jul 24, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-66007.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk-0.24%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍datasets

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`datasets`	all versions	5.0.1`pip install --upgrade 'datasets==5.0.1'`

Affected Products

1 product · 1 configurations

Application

datasetshuggingface

≤ 5.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasets, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update datasets to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-66007 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This path traversal vulnerability in the `datasets` library allows for information disclosure. An attacker could exploit this by providing specially crafted `file_name` metadata to a folder-based dataset builder, which, upon user interaction with `save_to_disk` or `push_to_hub` operations, could embed arbitrary local…

Workaround published by Red Hat

To mitigate this issue, ensure that all `file_name` metadata processed by the `datasets` library, especially within folder-based dataset builders, is thoroughly validated and sanitized. Avoid processing `file_name` values from untrusted sources without strict input validation to prevent directory traversal sequences. This will prevent the embedding of arbitrary local files during `save_to_disk` or `push_to_hub` operations.

Source: Red Hat security advisory for CVE-2026-66007 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat AI Inference Server 3.5	`rhaii/vllm-spyre-rhel9:1791818357`	RHSA-2026:82371
Red Hat OpenShift AI 2.25	`rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9:1791867208`	RHSA-2026:87410
Red Hat OpenShift AI 3.4	`rhoai/odh-autorag-rhel9:1791557539`	RHSA-2026:84734
Red Hat OpenShift AI 3.5	`rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9:1791816487`	RHSA-2026:86891

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-66007 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works