# CVE-2026-23745: node-tar Vulnerable to Arbitrary File Overwrite and Symlink Poisoning via Insufficient Path Sanitization > Attackers can overwrite arbitrary files or poison symlinks via malicious tar archives, potentially leading to code execution. - **Severity:** High 8.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`) - **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:** 16 Jan 2026 - **Updated:** 7 Sep 2026 - **Also known as:** CLEANSTART-2026-FG94911, CLEANSTART-2026-ZI47888, DEBIAN-CVE-2026-23745, ECHO-fcdb-3d59-4763, GHSA-8qq5-rm4j-mr97, MINI-3636-4c9j-259m, MINI-3f36-7mqg-5q65, MINI-4mpm-j62v-6cxr, MINI-5c66-f5jq-g3f8, MINI-68pj-jw9h-44vc, MINI-6jcp-3rpj-qcfj, MINI-6r9q-6v2x-g4pj, MINI-73v6-x73f-q67w, MINI-7gvw-5qr4-p62c, MINI-94qm-p32v-9q45, MINI-9vgr-hgqw-7cx4, MINI-g8ff-x4cp-2c64, MINI-gcgf-7xmx-7726, MINI-gw8f-6w42-39r7, MINI-h6cg-5xcg-75v6, MINI-hg28-9pqh-8h98, MINI-hpvp-6w3c-5xvq, MINI-hvv9-w77w-98qc, MINI-r22j-jvv2-r84q, MINI-rhxr-pmmm-jvxx, MINI-vq7x-6g9c-qq2r, MINI-xj9x-8cr4-m5r4, ROOT-APP-NPM-CVE-2026-23745, UBUNTU-CVE-2026-23745 ## What is CVE-2026-23745? CVE-2026-23745 is a high-severity path traversal vulnerability in isaacs node-tar, published on 16 Jan 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 Tar for Node.js. The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets. This vulnerability is fixed in 7.5.3. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-23745? 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.3 | | `tar` | npm | All versions | 7.5.3 | Products: Isaacs Tar. ## How do I fix CVE-2026-23745? Upgrade tar to 7.5.3 or later. ## Is CVE-2026-23745 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23745 exists. Public exploit code: - Proof of Concept for CVE-2026-23745: Arbitrary File Overwrite vulnerability in node-tar (versions < 7.5.3). (github_poc): https://github.com/Jvr2022/CVE-2026-23745 - Mirror of isaacs/node-tar pinned at 8bb83f7 — the commit before the CVE-2026-23745 fix. Demo target for autonomous vulnerability patching. Do not install from here; use node-tar 7.5.3+. (github_poc): https://github.com/OndrejDrapalik/node-tar-cve-demo - https://github.com/Novem13th/CVE-2026-23745-via-graphql-DEMO (github_poc): https://github.com/Novem13th/CVE-2026-23745-via-graphql-DEMO ## 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-29786](https://insights.sbomify.com/CVE-2026-29786/): node-tar: Hardlink Path Traversal via Drive-Relative Linkpath (high 8.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-23745 and fix it if it is affected. What it is: CVE-2026-23745 is a high-severity path traversal vulnerability in isaacs node-tar, published on 16 Jan 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-23745 exists. Affected packages and fixed versions: - tar (npm): affected all versions; fixed in 7.5.3 - tar (npm): affected all versions; fixed in 7.5.3 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-23745/ (Markdown: https://insights.sbomify.com/CVE-2026-23745/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23745 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23745 - OSV: https://osv.dev/vulnerability/CVE-2026-23745 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-23745/ Summaries are generated and may contain mistakes; the official description above is the record.