Findings

CVE-2015-1197

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.

Published Feb 19, 2015 · updated Oct 15, 2026 · gnu cpio

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.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 19, 2015 · NIST NVD

    Detected

    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.

  2. Oct 14, 2026 · NIST NVD

    Updated

    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.

  3. Oct 15, 2026 · OSV.dev

    Fix available

    cpio fixed in 2.11+dfsg-4.1; cpio fixed in 2.11+dfsg-4.1; cpio fixed in 2.11+dfsg-4.1

  4. Oct 15, 2026 · OSV.dev

    Fix available

    cpio fixed in 2.11+dfsg-4.1

  5. Oct 15, 2026 · OSV.dev

    Updated

    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.

Affected

  • Debian:12 cpio0 → 2.11+dfsg-4.1
  • Debian:13 cpio0 → 2.11+dfsg-4.1
  • Debian:14 cpio0 → 2.11+dfsg-4.1
  • cpe gnu/cpio2.11

Sources

References