CVE-2026-66485 is an uncontrolled memory allocation vulnerability in GNU cpio through version 2.15 in the make_path function in src/makepath.c. During archive extraction, make_path uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname. A malicious cpio archive containing a sufficiently long nested pathname can cause an unbounded stack allocation, leading to stack overflow and termination of the cpio process.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced by an AlmaLinux 9.6 local security-check advisory. The provided content supplies no technical description or affected-package details for this CVE.
A cpio memory-management vulnerability in make_path that can cause denial of service when processing a crafted archive.
A memory-management flaw in cpio's make_path function that can cause denial of service when processing a crafted archive.
A referenced vulnerability listed in the advisory metadata, without technical details in the provided content.
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.