Skip to main content

GNU cpio CVE-2026-66484

| EUVDEUVD-2026-55256 MEDIUM
Path Traversal (CWE-22)
2026-08-10 CERT-PL GHSA-rc3p-p5w3-fm9j
4.6
CVSS 4.0 · Vendor: CERT-PL
Share

Severity by source

Vendor (CERT-PL) PRIMARY
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
3.6 LOW

Local execution, no privileges required to supply or extract archive; scope changes because hard links escape extraction directory; user must actively run cpio on the malicious input.

3.1 AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
SUSE
3.3 MEDIUM
AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Red Hat
3.3 LOW
qualitative

Primary rating from Vendor (CERT-PL).

CVSS VectorVendor: CERT-PL

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
A
Scope
X

Lifecycle Timeline

2
Analysis Generated
Aug 10, 2026 - 11:08 vuln.today
CVE Published
Aug 10, 2026 - 10:25 cve.org
MEDIUM 4.6

DescriptionCVE.org

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

AnalysisAI

Hard-link path traversal in GNU cpio's tar extraction mode enables an attacker-controlled archive to create hard links pointing to files outside the intended extraction directory, defeating the security boundary that --no-absolute-filenames is designed to enforce. All GNU cpio versions tracked under CPE cpe:2.3:a:gnu:cpio:*:*:*:*:*:*:*:* are affected when processing tar archives in copy-in mode; the upstream fix exists only as a source commit with no tagged release confirmed at time of analysis. No active exploitation has been identified (no CISA KEV listing, no public exploit code), and exploitation requires a user to actively extract an attacker-supplied archive, materially constraining opportunistic risk.

Technical ContextAI

GNU cpio (CPE: cpe:2.3:a:gnu:cpio:*:*:*:*:*:*:*:*) is a Unix archiving utility that supports multiple formats including its native binary/newc formats and tar. In copy-in mode (cpio -i), cpio reads archive entries and writes them to the filesystem. The --no-absolute-filenames flag is documented to strip absolute path prefixes from extracted entries, preventing writes outside the extraction directory. The defect, classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), is an inconsistent sanitization between two code paths: regular file entries receive path normalization, but tar hard-link entries do not - the linkname field from the tar header is passed directly to link_to_name and subsequently to the link() system call without equivalent sanitization. A crafted tar archive entry with type flag set to hard-link and linkname set to an absolute path (e.g., /etc/passwd) bypasses the flag's guarantee. CERT-PL discovered and reported this asymmetric sanitization gap; the upstream fix is commit e2b9cbdd3354d2b1569b7390d1bc15c1930559ad in the GNU cpio Git repository.

RemediationAI

The upstream fix is commit e2b9cbdd3354d2b1569b7390d1bc15c1930559ad in the GNU cpio repository at https://git.savannah.gnu.org/cgit/cpio.git; no tagged release incorporating this fix has been confirmed at time of analysis, so the primary action is to monitor Linux distribution security channels (RHEL/CentOS, Debian, Ubuntu, Fedora errata) for updated cpio packages and apply them as part of routine patching. As an interim compensating control for environments processing untrusted archives, replace cpio-based extraction with GNU tar (tar -x) invoked inside a chroot or container to enforce filesystem namespace isolation - this removes the entire vulnerable code path at the cost of tooling changes in existing scripts. Alternatively, post-extraction audits using find <destdir> -type f -links +1 can detect unexpected hard links created during extraction, providing a detective control that identifies exploitation attempts without preventing them. Avoid extracting tar archives from untrusted sources using cpio until a patched package is available from your distribution vendor. The CERT-PL advisory at https://cert.pl/en/posts/2026/08/CVE-2026-66484 should be monitored for patched version announcements.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SLES15-SP5-CHOST-BYOS-SAP-CCloud Affected
SLES15-SP6-CHOST-BYOS Affected
SLES15-SP6-CHOST-BYOS-Aliyun Affected
SLES15-SP6-CHOST-BYOS-Azure Affected
SLES15-SP6-CHOST-BYOS-EC2 Affected

Share

CVE-2026-66484 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy