# CVE-2026-29786: node-tar: Hardlink Path Traversal via Drive-Relative Linkpath > Attackers can overwrite files outside the extraction directory by crafting tar archives with drive-relative hardlink targets in node-tar. - **Severity:** High 8.2 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 7 Mar 2026 - **Updated:** 1 Sep 2026 - **Also known as:** 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 ## What is CVE-2026-29786? 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. ### Official 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. Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-29786? 2 open source packages ship an affected version, including tar. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tar` | npm | All versions | 7.5.10 | | `tar` | npm | All versions | 7.5.10 | Products: Isaacs Tar. ## How do I fix CVE-2026-29786? Upgrade tar to 7.5.10 or later. ## Is CVE-2026-29786 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29786 exists. Public exploit code: - PoC for CVE-2026-29786 demonstrating a node-tar hardlink path traversal that allows overwriting files outside the extraction directory. (github_poc): https://github.com/Jvr2022/CVE-2026-29786 - 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) (github_poc): https://github.com/Rohitberiwala/NodeJS-Tar-Symlink-Exploit-CVE-2026-29786 ## Other vulnerabilities in isaacs node-tar - [CVE-2026-59873](https://insights.sbomify.com/CVE-2026-59873/): node-tar: Decompression/parse DoS via unlimited input (critical 9.2) - [CVE-2026-23950](https://insights.sbomify.com/CVE-2026-23950/): node-tar has Race Condition in Path Reservations via Unicode Ligature Collisions on macOS APFS (high 8.8) - [CVE-2026-59874](https://insights.sbomify.com/CVE-2026-59874/): node-tar: Negative tar entry size causes infinite loop in archive replace (high 8.7) - [CVE-2026-31802](https://insights.sbomify.com/CVE-2026-31802/): node-tar Symlink Path Traversal via Drive-Relative Linkpath (high 8.2) - [CVE-2026-24842](https://insights.sbomify.com/CVE-2026-24842/): node-tar Vulnerable to Arbitrary File Creation/Overwrite via Hardlink Path Traversal (high 8.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-29786 and fix it if it is affected. What 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. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29786 exists. Affected packages and fixed versions: - tar (npm): affected all versions; fixed in 7.5.10 - tar (npm): affected all versions; fixed in 7.5.10 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-29786/ (Markdown: https://insights.sbomify.com/CVE-2026-29786/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29786 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29786 - OSV: https://osv.dev/vulnerability/CVE-2026-29786 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-29786/ Summaries are generated and may contain mistakes; the official description above is the record.