{"id":"CVE-2026-66485","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-66485","generatedAt":"2026-10-28T10:46:54.711Z","title":"GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c.","description":"GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.\n\nThis issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9","published":"2026-08-10T11:17:28.000Z","lastModified":"2026-10-24T16:10:00.000Z","status":"Deferred","sourceIdentifier":"cvd@cert.pl","cvss":{"version":"4.0","score":4.6,"severity":"MEDIUM","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M"},"cwe":["CWE-789"],"affected":[],"epss":{"score":0.00185,"percentile":0.08053,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.18%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://cert.pl/en/posts/2026/08/CVE-2026-66484","source":"cvd@cert.pl"},{"url":"https://git.savannah.gnu.org/cgit/cpio.git","source":"cvd@cert.pl"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-66485","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}