{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-66484 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-66484 is a medium-severity path traversal vulnerability in GNU cpio, published on 10 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-66484 and fix it if it is affected.\n\nWhat it is: CVE-2026-66484 is a medium-severity path traversal vulnerability in GNU cpio, published on 10 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-66484 in the wild and no public exploit code.\n\nAffected product: GNU cpio. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-66484/ (Markdown: https://insights.sbomify.com/CVE-2026-66484/index.md)","id":"CVE-2026-66484","markdown":"https://insights.sbomify.com/CVE-2026-66484/index.md","name":"CVE-2026-66484","record":{"aliases":["AZL-94695","DEBIAN-CVE-2026-66484","GHSA-rc3p-p5w3-fm9j","RHSA-2026:54508","UBUNTU-CVE-2026-66484"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"GNU cpio utility","requires_auth":"none","summary":"Attackers can create hard links to external files during tar extraction, bypassing security restrictions in GNU cpio.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.\n\nThis issue has been fixed in commit e2b9cbdd3354d2b1569b7390d1bc15c1930559ad","ecosystems":["Red Hat:hummingbird:1"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Path Traversal in GNU cpio","id":"CVE-2026-66484","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Uncontrolled Memory Allocation in GNU cpio","id":"CVE-2026-66485"},"packages":[{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:2.15-10.1.hum1"],"introduced":["0"],"last_affected":[],"package":"cpio","purl":"pkg:rpm/redhat/cpio","source":"RHSA-2026:54508"}],"prev":{"headline":"WordPress Education Center theme \u003c= 3.6.12 - PHP Object Injection vulnerability","id":"CVE-2026-66483"},"products":["cpio"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["GNU"]},"summary":"Attackers can create hard links to external files during tar extraction, bypassing security restrictions in GNU cpio.","url":"https://insights.sbomify.com/CVE-2026-66484/"}