{"answers":{"affected":"2 open source packages ship an affected version, including tar. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26960 in the wild and no public exploit code.","fix":"Upgrade tar to 7.5.8 or later.","what":"CVE-2026-26960 is a high-severity path traversal vulnerability in isaacs node-tar, published on 20 Feb 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-26960 and fix it if it is affected.\n\nWhat it is: CVE-2026-26960 is a high-severity path traversal vulnerability in isaacs node-tar, published on 20 Feb 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-26960 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tar (npm): affected all versions; fixed in 7.5.8\n- tar (npm): affected all versions; fixed in 7.5.8\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-26960/ (Markdown: https://insights.sbomify.com/CVE-2026-26960/index.md)","id":"CVE-2026-26960","markdown":"https://insights.sbomify.com/CVE-2026-26960/index.md","name":"CVE-2026-26960","record":{"aliases":["CLEANSTART-2026-IA47367","CLEANSTART-2026-NN34341","DEBIAN-CVE-2026-26960","ECHO-73e4-b37f-d747","GHSA-83g3-92jg-28cx","MINI-2cmr-f274-j9g6","MINI-3fh2-fjfv-3c3v","MINI-3xgx-4g8r-hfhp","MINI-49jv-84xg-438c","MINI-587w-8hwq-g923","MINI-5pxv-cmwh-wxwm","MINI-72vf-gv8w-wpgm","MINI-7fm7-wfqh-mqq8","MINI-7vp2-q4cx-v885","MINI-8cww-cp47-m2rc","MINI-8jjm-6rcc-jrqc","MINI-8rpw-7377-68vg","MINI-c294-457x-5h47","MINI-f88r-m7m5-7mqj","MINI-h4xc-4crp-9jw3","MINI-h84h-chmg-9whc","MINI-hm3j-36wp-657f","MINI-hv8g-xx57-q6w9","MINI-j244-8hr5-rvrf","MINI-p734-h8hc-h9vq","MINI-pj9h-cr93-j57w","MINI-vx32-76vq-33wp","MINI-wp7x-cxm8-7433","MINI-x9hf-3mv2-675j","MINI-xvr4-fg8w-j873","ROOT-APP-NPM-CVE-2026-26960","UBUNTU-CVE-2026-26960"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js tar library","requires_auth":"none","summary":"Attackers can read or write arbitrary files by crafting a tar archive with hardlinks escaping the extraction directory via symlinks.\n","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tar","vendor":"isaacs"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"node-tar is a full-featured Tar for Node.js. When using default options in versions 7.5.7 and below, an attacker-controlled archive can create a hardlink inside the extraction directory that points to a file outside the extraction root, enabling arbitrary file read and write as the extracting user. Severity is high because the primitive bypasses path protections and turns archive extraction into a direct filesystem access primitive. This issue has been fixed in version 7.5.8.","ecosystems":["npm"],"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":"node-tar has Arbitrary File Read/Write via Hardlink Target Escape Through Symlink Chain in Extraction","id":"CVE-2026-26960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Rack: Multipart Boundary Parsing Ambiguity allowing WAF Bypass","id":"CVE-2026-26961"},"packages":[{"ecosystem":"npm","fixed":["7.5.8"],"introduced":["0"],"last_affected":[],"package":"tar","purl":null,"source":"GHSA-83g3-92jg-28cx"},{"ecosystem":"npm","fixed":["7.5.8"],"introduced":["0"],"last_affected":[],"package":"tar","purl":"pkg:npm/tar","source":"GHSA-83g3-92jg-28cx"}],"prev":{"headline":"ADB Explorer Vulnerable to RCE via Insufficient Input Validation","id":"CVE-2026-26959"},"products":["node-tar"],"published":"2026-02-20","related":[{"cvss_score":9.2,"headline":"node-tar: Decompression/parse DoS via unlimited input","id":"CVE-2026-59873","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":8.8,"headline":"node-tar has Race Condition in Path Reservations via Unicode Ligature Collisions on macOS APFS","id":"CVE-2026-23950","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":8.7,"headline":"node-tar: Negative tar entry size causes infinite loop in archive replace","id":"CVE-2026-59874","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":8.2,"headline":"node-tar Symlink Path Traversal via Drive-Relative Linkpath","id":"CVE-2026-31802","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":8.2,"headline":"node-tar: Hardlink Path Traversal via Drive-Relative Linkpath","id":"CVE-2026-29786","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":8.2,"headline":"node-tar Vulnerable to Arbitrary File Creation/Overwrite via Hardlink Path Traversal","id":"CVE-2026-24842","kev_date_added":null,"published":"2026-01-28"},{"cvss_score":8.2,"headline":"node-tar Vulnerable to Arbitrary File Overwrite and Symlink Poisoning via Insufficient Path Sanitization","id":"CVE-2026-23745","kev_date_added":null,"published":"2026-01-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2026-02-20","vendors":["isaacs"]},"summary":"Attackers can read or write arbitrary files by crafting a tar archive with hardlinks escaping the extraction directory via symlinks.\n","url":"https://insights.sbomify.com/CVE-2026-26960/"}