Quick answers
- Is CVE-2026-66486 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66486 being exploited in the wild.
- How severe is CVE-2026-66486?
- Informational severity, with a CVSS score of 0, published 10 August 2026.
- Which products and versions are affected?
- Gnu Cpio through 2.15.
- Is there a fix for CVE-2026-66486?
- A patch was published on 2026-07-23: Fix released in commit 2ff9600c9ef32e88759843cdbde74c8db5ae9b30 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66486 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-66486?
- Check whether you run Gnu Cpio at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a CWE-116 improper encoding/escaping flaw in cpio's archive member listing functionality. When cpio lists archive members via the -it command, member names are printed directly to output without quoting or escaping special characters. An attacker can craft a malicious cpio archive with member names containing embedded newline characters or ANSI escape sequences. These are rendered unescaped during listing, allowing injection of forged listing entries or terminal control sequences that manipulate terminal behavior. The issue is fixed in commit 2ff9600c9ef32e88759843cdbde74c8db5ae9b30 and affects cpio versions through 2.15.
Affected products
- GNU cpio through 2.15
Timeline
- 2026-08-10: disclosed
- 2026-07-23: patched: Fix released in commit 2ff9600c9ef32e88759843cdbde74c8db5ae9b30