Hugging Face Datasets up to 5.0.0 Folder-based Dataset Builders file_name path traversal

Summaryinfo

A vulnerability classified as problematic has been found in Hugging Face Datasets up to 5.0.0. This impacts an unknown function of the component Folder-based Dataset Builders. Performing a manipulation of the argument file_name results in path traversal. This vulnerability is identified as CVE-2026-66007. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in Hugging Face Datasets up to 5.0.0. This affects some unknown processing of the component Folder-based Dataset Builders. The manipulation of the argument file_name with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-66007 since 07/23/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Applying the patch f989ef9b4cc6c0039a7a82458eebca49e2b58b4b is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-48613). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Hugging Face

Name

• Datasets

Version

• 5.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion