CVE-2026-66485 is an uncontrolled memory allocation vulnerability in GNU cpio affecting versions through 2.15. The flaw is located in the make_path function in src/makepath.c, where stack memory is allocated with alloca based on the length of argpath. During archive extraction, argpath is derived from a pathname fully controlled by archive contents. A crafted cpio archive containing a sufficiently long nested pathname can therefore trigger an unbounded stack allocation on the process stack, leading to stack overflow and termination of the cpio process. The issue is exploitable during extraction of malicious archives and results in denial of service.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An uncontrolled memory allocation vulnerability in GNU cpio that can trigger unbounded stack allocation via a crafted archive pathname, causing stack overflow and denial of service.
A vulnerability reported by CERT Polska as affecting GNU cpio software.
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.