OESA-2026-3456 (CVE-2026-66484)
Vulnerability from osv_openeuler – Published: 2026-08-20 10:00 – Updated: 2026-08-20 10:00 – Source websiteGNU cpio copies files into or out of a cpio or tar archive. The archive can be another file on the disk, a magnetic tape, or a pipe.
Security Fix(es):
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(CVE-2026-66484)
GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.
This issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9(CVE-2026-66485)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"cpio-2.13-9.oe2003sp4.aarch64.rpm",
"cpio-debuginfo-2.13-9.oe2003sp4.aarch64.rpm",
"cpio-debugsource-2.13-9.oe2003sp4.aarch64.rpm"
],
"noarch": [
"cpio-help-2.13-9.oe2003sp4.noarch.rpm"
],
"src": [
"cpio-2.13-9.oe2003sp4.src.rpm"
],
"x86_64": [
"cpio-2.13-9.oe2003sp4.x86_64.rpm",
"cpio-debuginfo-2.13-9.oe2003sp4.x86_64.rpm",
"cpio-debugsource-2.13-9.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "cpio",
"purl": "pkg:rpm/openEuler/cpio\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13-9.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"cpio-2.13-12.oe2203sp4.aarch64.rpm",
"cpio-debuginfo-2.13-12.oe2203sp4.aarch64.rpm",
"cpio-debugsource-2.13-12.oe2203sp4.aarch64.rpm"
],
"noarch": [
"cpio-help-2.13-12.oe2203sp4.noarch.rpm"
],
"src": [
"cpio-2.13-12.oe2203sp4.src.rpm"
],
"x86_64": [
"cpio-2.13-12.oe2203sp4.x86_64.rpm",
"cpio-debuginfo-2.13-12.oe2203sp4.x86_64.rpm",
"cpio-debugsource-2.13-12.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "cpio",
"purl": "pkg:rpm/openEuler/cpio\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13-12.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"cpio-2.14-5.oe2403sp1.aarch64.rpm",
"cpio-debuginfo-2.14-5.oe2403sp1.aarch64.rpm",
"cpio-debugsource-2.14-5.oe2403sp1.aarch64.rpm"
],
"noarch": [
"cpio-help-2.14-5.oe2403sp1.noarch.rpm"
],
"src": [
"cpio-2.14-5.oe2403sp1.src.rpm"
],
"x86_64": [
"cpio-2.14-5.oe2403sp1.x86_64.rpm",
"cpio-debuginfo-2.14-5.oe2403sp1.x86_64.rpm",
"cpio-debugsource-2.14-5.oe2403sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP1",
"name": "cpio",
"purl": "pkg:rpm/openEuler/cpio\u0026distro=openEuler-24.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.14-5.oe2403sp1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"cpio-2.14-5.oe2403sp3.aarch64.rpm",
"cpio-debuginfo-2.14-5.oe2403sp3.aarch64.rpm",
"cpio-debugsource-2.14-5.oe2403sp3.aarch64.rpm"
],
"noarch": [
"cpio-help-2.14-5.oe2403sp3.noarch.rpm"
],
"src": [
"cpio-2.14-5.oe2403sp3.src.rpm"
],
"x86_64": [
"cpio-2.14-5.oe2403sp3.x86_64.rpm",
"cpio-debuginfo-2.14-5.oe2403sp3.x86_64.rpm",
"cpio-debugsource-2.14-5.oe2403sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP3",
"name": "cpio",
"purl": "pkg:rpm/openEuler/cpio\u0026distro=openEuler-24.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.14-5.oe2403sp3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"cpio-2.14-5.oe2403sp4.aarch64.rpm",
"cpio-debuginfo-2.14-5.oe2403sp4.aarch64.rpm",
"cpio-debugsource-2.14-5.oe2403sp4.aarch64.rpm"
],
"noarch": [
"cpio-help-2.14-5.oe2403sp4.noarch.rpm"
],
"src": [
"cpio-2.14-5.oe2403sp4.src.rpm"
],
"x86_64": [
"cpio-2.14-5.oe2403sp4.x86_64.rpm",
"cpio-debuginfo-2.14-5.oe2403sp4.x86_64.rpm",
"cpio-debugsource-2.14-5.oe2403sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP4",
"name": "cpio",
"purl": "pkg:rpm/openEuler/cpio\u0026distro=openEuler-24.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.14-5.oe2403sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "GNU cpio copies files into or out of a cpio or tar archive. The archive can be another file on the disk, a magnetic tape, or a pipe.\r\n\r\nSecurity Fix(es):\n\nGNU 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.\n\nThis issue has been fixed in commit e2b9cbdd3354d2b1569b7390d1bc15c1930559ad(CVE-2026-66484)\n\nGNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.\n\nThis issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9(CVE-2026-66485)",
"id": "OESA-2026-3456",
"modified": "2026-08-20T10:00:01Z",
"published": "2026-08-20T10:00:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3456"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-66484"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-66485"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
],
"summary": "cpio security update",
"upstream": [
"CVE-2026-66484",
"CVE-2026-66485"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.