GNU Cpio vulnerabilities

15 CVEs affecting GNU Cpio, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-66486, published 2026-08-10.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2014-9112, published 2014-12-02. Medium severity, CVSS 5.0. EPSS: 7.1% chance of exploitation in the next 30 days. Heap-based buffer overflow in the process_copy_in function in GNU Cpio 2.11 allows remote attackers to cause a denial of service via a large block value in a cpio archive.
CVE-2016-2037, published 2016-02-22. Medium severity, CVSS 6.5. EPSS: 5.5% chance of exploitation in the next 30 days. The cpio_safer_name_suffix function in util.c in cpio 2.11 allows remote attackers to cause a denial of service (out-of-bounds write) via a crafted cpio file.
CVE-2010-0624, published 2010-03-15. Medium severity, CVSS 6.8. EPSS: 4.7% chance of exploitation in the next 30 days. Heap-based buffer overflow in the rmt_read__ function in lib/rtapelib.c in the rmt client functionality in GNU tar before 1.23 and GNU cpio before 2.11 allows remote rmt servers to cause a denial of…
CVE-2021-38185, published 2021-08-08. High severity, CVSS 7.8. EPSS: 4.2% chance of exploitation in the next 30 days. GNU cpio through 2.13 allows attackers to execute arbitrary code via a crafted pattern file, because of a dstring.c ds_fgetstr integer overflow that triggers an out-of-bounds heap write. NOTE: it is…
CVE-2010-4226, published 2014-02-06. High severity, CVSS 7.2. EPSS: 2.9% chance of exploitation in the next 30 days. cpio, as used in build 2007.05.10, 2010.07.28, and possibly other versions, allows remote attackers to overwrite arbitrary files via a symlink within an RPM package archive.
CVE-2015-1197, published 2015-02-19. Low severity, CVSS 1.9. EPSS: 2.9% chance of exploitation in the next 30 days. cpio 2.11, when using the --no-absolute-filenames option, allows local users to write to arbitrary files via a symlink attack on a file in an archive.
CVE-2005-1229, published 2005-05-02. Medium severity, CVSS 4.6. EPSS: 2.1% chance of exploitation in the next 30 days. Directory traversal vulnerability in cpio 2.6 and earlier allows remote attackers to write to arbitrary directories via a .. (dot dot) in a cpio file.
CVE-2023-7207, published 2024-02-29. Medium severity, CVSS 4.9. EPSS: 0.9% chance of exploitation in the next 30 days. Debian's cpio contains a path traversal vulnerability. This issue was introduced by reverting CVE-2015-1197 patches which had caused a regression in --no-absolute-filenames. Upstream has since…
CVE-2023-7216, published 2024-02-05. Medium severity, CVSS 5.3. EPSS: 0.9% chance of exploitation in the next 30 days. A path traversal vulnerability was found in the CPIO utility. This issue could allow a remote unauthenticated attacker to trick a user into opening a specially crafted archive. During the extraction…
CVE-2019-14866, published 2020-01-07. High severity, CVSS 7.3. EPSS: 0.7% chance of exploitation in the next 30 days. In all versions of cpio before 2.13 does not properly validate input files when generating TAR archives. When cpio is used to create TAR archives from paths an attacker can write to, the resulting…

Latest

CVE-2026-66486, published 2026-08-10. Medium severity, CVSS 4.6. EPSS: 0.2% chance of exploitation in the next 30 days. GNU cpio is vulnerable to improper encoding or escaping of output in its archive member listing functionality. When listing archive members via cpio -it, member names are printed directly to output…
CVE-2026-66485, published 2026-08-10. Medium severity, CVSS 4.6. EPSS: 0.2% chance of exploitation in the next 30 days. 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…
CVE-2026-66484, published 2026-08-10. Medium severity, CVSS 4.6. EPSS: 0.2% chance of exploitation in the next 30 days. GNU cpio contains a Path Traversal vulnerability in its tar archive extraction functionality. When extracting a tar archive in copy-in mode with the --no-absolute-filenames option, the extracted file…