CVE-2026-66484 is a path-traversal flaw in GNU cpio tar archive extraction. In copy-in mode, when --no-absolute-filenames is used, cpio normalizes the archive member pathname but does not apply equivalent sanitization to a tar hard-link entry's link target before passing it to the hard-link creation logic. A crafted tar archive can therefore specify an absolute hard-link target outside the extraction directory, defeating the expected containment provided by --no-absolute-filenames. GNU cpio versions through 2.15 are affected. The upstream fix sanitizes the hard-link target before link creation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A cpio tar-archive extraction flaw that permits a crafted archive to create hard links outside the intended extraction directory.
A cpio tar-archive extraction sanitization flaw that permits a malicious archive to create hard links outside the intended extraction directory.
A referenced vulnerability listed in the advisory metadata, without technical details in the provided content.
A path traversal vulnerability in GNU cpio tar archive extraction that allows a crafted archive to create a hard link to an existing file outside the intended extraction directory, bypassing the expected protection of --no-absolute-filenames.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.