cve.bz

CVE-2026-66484 gnu cpio: Path traversal

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 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 name is normalized but the tar hard-link target is passed to the link_to_name function without equivalent sanitization before calling link function. A tar archive provided by an attacker, containing a hard-link entry whose linkname is set to an absolute path outside the extraction directory, can cause cpio to create a hard link to an existing file outside the intended extraction directory, breaking the expected guarantee of --no-absolute-filenames and allowing archive-controlled linkage to external files. This issue has been fixed in commit e2b9cbdd3354d2b1569b7390d1bc15c1930559ad

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:L/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; 9th 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-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
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-66484 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-66484?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-66484?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-66484 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-66484

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-66484](https://cve.bz/cve/badge/CVE-2026-66484.svg)](https://cve.bz/cve/CVE-2026-66484)

HTML:

<a href="https://cve.bz/cve/CVE-2026-66484"><img src="https://cve.bz/cve/badge/CVE-2026-66484.svg" alt="CVE-2026-66484"></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-66484
Ubuntu22.04:LTScpio2.13+dfsg-7ubuntu0.2UBUNTU-CVE-2026-66484 USN-8704-1
Ubuntu24.04:LTScpio2.15+dfsg-1ubuntu2.1UBUNTU-CVE-2026-66484 USN-8704-1
Ubuntu26.04:LTScpio2.15+dfsg-2.1ubuntu0.1UBUNTU-CVE-2026-66484 USN-8704-1
UbuntuPro:14.04:LTScpio2.11+dfsg-1ubuntu1.2+esm3UBUNTU-CVE-2026-66484 USN-8704-1
UbuntuPro:16.04:LTScpio2.11+dfsg-5ubuntu1.1+esm2UBUNTU-CVE-2026-66484 USN-8704-1
UbuntuPro:18.04:LTScpio2.12+dfsg-6ubuntu0.18.04.4+esm1UBUNTU-CVE-2026-66484 USN-8704-1
UbuntuPro:20.04:LTScpio2.13+dfsg-2ubuntu0.4+esm1UBUNTU-CVE-2026-66484 USN-8704-1
Red Hathummingbird:1cpio0:2.15-10.1.hum1RHSA-2026:54508
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-94695

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 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 · Red Hat · SUSE · openSUSE.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A path traversal flaw was found in GNU cpio. When extracting tar archives in copy-in mode with the --no-absolute-filenames option, the hard-link target name is not sanitized. An attacker could provide a specially crafted tar archive that, when extracted with this option, creates hard links pointing to files outside the intended extraction directory, potentially leading to unauthorized file modifications.

Red Hat's mitigation

Avoid using the --no-absolute-filenames option when extracting untrusted archives with cpio.

ProductPackageStateAdvisory
Red Hat Hardened Imagescpio-main-2.15-10.1.hum1Fixed 2026-08-13RHSA-2026:54508
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

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-66484.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

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

References

Check your stackJSON