Arbitrary file truncation via symlink race
Published Aug 20, 2026 · Updated Aug 20, 2026
Symlink race in the LocalStore restore path in Nix before 2.35.0 allows local users to truncate files outside the sandbox. During restore, writeFile can open a path with O_TRUNC after a final symlink is swapped, following that symlink instead of enforcing FinalSymlink::DontFollow. Exploitation requires the recursive-nix experimental feature, a malicious derivation, and winning the race, and it yields only empty-file creation or truncation with nix or nix-daemon permissions.
Summary
What happened
Symlink race in the LocalStore restore path in Nix before 2.35.0 allows local users to truncate files outside the sandbox. During restore, writeFile can open a path with O_TRUNC after a final symlink is swapped, following that symlink instead of enforcing FinalSymlink::DontFollow. Exploitation requires the recursive-nix experimental feature, a malicious derivation, and winning the race, and it yields only empty-file creation or truncation with nix or nix-daemon permissions.
The record
- CVE
- CVE-2026-64846
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- NixOS
- Product
- Nix
- Classifications
- CWE-367, CWE-61
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 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=< 2.35.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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