External file linkage via unsanitized hard-link targets
Published Aug 10, 2026 · Updated Aug 10, 2026
Path traversal in GNU Project cpio 2.15 and earlier allows attackers to create hard links outside the extraction directory via a crafted tar archive. In copy-in mode, --no-absolute-filenames normalizes the member name but passes the tar hard-link target to link_to_name without equivalent sanitization. Exploitation requires extraction with that option and can link an archive-controlled path to an existing file accessible to the cpio process.
Summary
What happened
Path traversal in GNU Project cpio 2.15 and earlier allows attackers to create hard links outside the extraction directory via a crafted tar archive. In copy-in mode, --no-absolute-filenames normalizes the member name but passes the tar hard-link target to link_to_name without equivalent sanitization. Exploitation requires extraction with that option and can link an archive-controlled path to an existing file accessible to the cpio process.
The record
- CVE
- CVE-2026-66484
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The GnuPG Project
- Product
- GNU cpio
- Classifications
- CWE-22, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 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 <=2.15
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