cve.bz

CVE-2026-66486 gnu cpio: Improper Encoding or Escaping of Output

4.6 mediumEPSS 0.2%

Medium (4.6) in gnu cpio. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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 without quoting or escaping. An attacker can craft a cpio archive containing member names with embedded newline characters or ANSI escape sequences, causing forged listing entries or terminal control sequence injection when the listing is displayed. This issue has been fixed in commit 2ff9600c9ef32e88759843cdbde74c8db5ae9b30

Severity

CVSS 4.0

4.6 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-116 Improper Encoding or Escaping of Output
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-66486 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-66486?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-66486?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-66486 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-66486

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-66486](https://cve.bz/cve/badge/CVE-2026-66486.svg)](https://cve.bz/cve/CVE-2026-66486)

HTML:

<a href="https://cve.bz/cve/CVE-2026-66486"><img src="https://cve.bz/cve/badge/CVE-2026-66486.svg" alt="CVE-2026-66486"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GNU cpiothrough 2.15

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14cpiono fix listedDEBIAN-CVE-2026-66486
Ubuntu22.04:LTScpio2.13+dfsg-7ubuntu0.2UBUNTU-CVE-2026-66486 USN-8704-1
Ubuntu24.04:LTScpio2.15+dfsg-1ubuntu2.1UBUNTU-CVE-2026-66486 USN-8704-1
Ubuntu26.04:LTScpio2.15+dfsg-2.1ubuntu0.1UBUNTU-CVE-2026-66486 USN-8704-1
UbuntuPro:14.04:LTScpio2.11+dfsg-1ubuntu1.2+esm3UBUNTU-CVE-2026-66486 USN-8704-1
UbuntuPro:16.04:LTScpio2.11+dfsg-5ubuntu1.1+esm2UBUNTU-CVE-2026-66486 USN-8704-1
UbuntuPro:18.04:LTScpio2.12+dfsg-6ubuntu0.18.04.4+esm1UBUNTU-CVE-2026-66486 USN-8704-1
UbuntuPro:20.04:LTScpio2.13+dfsg-2ubuntu0.4+esm1UBUNTU-CVE-2026-66486 USN-8704-1
SUSELinux Enterprise Micro 5.3, Linux Enterprise Micro 5.4, Linux Enterprise Micro 5.5 and 1 morecpio2.13-150400.3.10.1SUSE-SU-2026:4012-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0cpio2.15-160000.3.1SUSE-SU-2026:23612-1
SUSELinux Enterprise Server LTSS Extended Security 12 SP5cpio2.11-36.25.1SUSE-SU-2026:3959-1
SUSELinux Micro 6.0cpio2.15-2.1SUSE-SU-2026:23441-1
SUSELinux Micro 6.1cpio2.15-slfo.1.1_3.1SUSE-SU-2026:23355-1
SUSELinux Micro 6.2cpio2.15-160000.3.1SUSE-SU-2026:23464-1
openSUSELeap 16.0cpio2.15-160000.3.1openSUSE-SU-2026:21747-1
openSUSETumbleweedcpio2.15-8.1openSUSE-SU-2026:11618-1
Azure Linux3cpio2.14-2AZL-94689

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

GNU cpio's archive-listing function (cpio -it) prints member names without escaping, allowing a crafted archive to inject terminal control sequences or forge listing entries when a user lists its contents. All Red Hat cpio packages (RHEL 6 through 10, RHIVOS) ship versions well below the fix and are affected.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Users should avoid listing archives from untrusted sources, or pipe listing output through a filter that strips control characters.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10cpioFix deferred
Red Hat Enterprise Linux 6cpioFix deferred
Red Hat Enterprise Linux 7cpioFix deferred
Red Hat Enterprise Linux 8cpioFix deferred
Red Hat Enterprise Linux 9cpioFix deferred
Red Hat Hardened ImagescpioAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-66486.

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON