Arbitrary file write via surviving extraction symlink
Published Jul 23, 2026 · Updated Jul 23, 2026
Symlink following in Hugging Face Datasets 5.0.0 and earlier allows local users to write arbitrary files during archive extraction. Extractor.extract() silently ignores shutil.rmtree() failing on a symlinked output path, then format-specific extractors follow that surviving link and unpack archive members into its target. Exploitation requires write access to a predictable shared-cache path and a victim extraction, allowing sensitive-file overwrite with the victim process's privileges.
Summary
What happened
Symlink following in Hugging Face Datasets 5.0.0 and earlier allows local users to write arbitrary files during archive extraction. Extractor.extract() silently ignores shutil.rmtree() failing on a symlinked output path, then format-specific extractors follow that surviving link and unpack archive members into its target. Exploitation requires write access to a predictable shared-cache path and a victim extraction, allowing sensitive-file overwrite with the victim process's privileges.
The record
- CVE
- CVE-2026-65010
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- Hugging Face
- Product
- Datasets
- Classifications
- CWE-61
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=5.00
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 8296 reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo