{"answers":{"affected":"2 open source packages ship an affected version, including tar. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29786 exists.","fix":"Upgrade tar to 7.5.10 or later.","what":"CVE-2026-29786 is a high-severity path traversal vulnerability in isaacs node-tar, published on 7 Mar 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-29786 and fix it if it is affected.\n\nWhat it is: CVE-2026-29786 is a high-severity path traversal vulnerability in isaacs node-tar, published on 7 Mar 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29786 exists.\n\nAffected packages and fixed versions:\n- tar (npm): affected all versions; fixed in 7.5.10\n- tar (npm): affected all versions; fixed in 7.5.10\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-29786/ (Markdown: https://insights.sbomify.com/CVE-2026-29786/index.md)","id":"CVE-2026-29786","markdown":"https://insights.sbomify.com/CVE-2026-29786/index.md","name":"CVE-2026-29786","record":{"aliases":["AZL-101772","AZL-79553","AZL-79556","CLEANSTART-2026-VD64269","CLEANSTART-2026-WV30852","CLSA-2026-1787146736","DEBIAN-CVE-2026-29786","ECHO-2138-3fe3-e5e0","GHSA-qffp-2rhf-9h96","MINI-2pq6-vvwh-pc2x","MINI-3m76-c3mh-vm97","MINI-3mpg-762w-6x4m","MINI-43f3-xmvx-j8f2","MINI-4h7x-h7gq-5x59","MINI-67g3-m4j2-94cx","MINI-6826-m9fp-4m68","MINI-79cc-cwg4-33hf","MINI-88p5-ww46-57pp","MINI-8r75-x7ch-j7vj","MINI-99pc-x4g4-h68w","MINI-cwjr-jqmf-8mq5","MINI-j3cj-c92w-vq8p","MINI-jppp-649v-3fq2","MINI-jx4p-x7vw-45v7","MINI-mg85-765q-r7vc","MINI-mvvv-rvp7-cg32","MINI-p4pw-xmr7-fmvh","MINI-rphh-qv3w-jx82","MINI-v2p3-q25w-9vxv","MINI-v784-c8gg-xffg","MINI-vwh9-wqmq-g54v","MINI-w55h-7m4v-2fr8","MINI-x46q-gj9j-c9v3","MINI-xgcj-r8c7-27q2","ROOT-APP-NPM-CVE-2026-29786","ROOT-APP-NPM-GHSA-qffp-2rhf-9h96","UBUNTU-CVE-2026-29786"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js tar library","requires_auth":"none","summary":"Attackers can overwrite files outside the extraction directory by crafting tar archives with drive-relative hardlink targets in node-tar.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tar","vendor":"isaacs"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"node-tar is a full-featured Tar for Node.js. Prior to version 7.5.10, tar can be tricked into creating a hardlink that points outside the extraction directory by using a drive-relative link target such as C:../target.txt, which enables file overwrite outside cwd during normal tar.x() extraction. This issue has been patched in version 7.5.10.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-03-05","github_poc":2,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-05T22:53:22Z","kind":"github_poc","ref":"https://github.com/Jvr2022/CVE-2026-29786","stars":1,"title":"PoC for CVE-2026-29786 demonstrating a node-tar hardlink path traversal that allows overwriting files outside the extraction directory."},{"date":"2026-03-10T06:40:34Z","kind":"github_poc","ref":"https://github.com/Rohitberiwala/NodeJS-Tar-Symlink-Exploit-CVE-2026-29786","stars":1,"title":"Technical analysis and Proof-of-Concept (PoC) for a critical Path Traversal vulnerability via Symlink manipulation in the Node.js 'tar' package (CVE-2026-29786)"}],"tier":"weaponised"},"has_fix":true,"headline":"node-tar: Hardlink Path Traversal via Drive-Relative Linkpath","id":"CVE-2026-29786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"mcp-memory-service: System Information Disclosure via Health Endpoint","id":"CVE-2026-29787"},"packages":[{"ecosystem":"npm","fixed":["7.5.10"],"introduced":["0"],"last_affected":[],"package":"tar","purl":null,"source":"GHSA-qffp-2rhf-9h96"},{"ecosystem":"npm","fixed":["7.5.10"],"introduced":["0"],"last_affected":[],"package":"tar","purl":"pkg:npm/tar","source":"GHSA-qffp-2rhf-9h96"}],"prev":{"headline":"NATS Server panic via malicious compression on leafnode port","id":"CVE-2026-29785"},"products":["node-tar"],"published":"2026-03-07","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 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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["isaacs"]},"summary":"Attackers can overwrite files outside the extraction directory by crafting tar archives with drive-relative hardlink targets in node-tar.","url":"https://insights.sbomify.com/CVE-2026-29786/"}