# CVE-2026-59875: node-tar: Uncaught Exception DoS via NUL byte in PAX path/linkpath records > A crafted tar archive with NUL bytes in PAX records causes an uncaught exception, crashing the application using the node-tar library. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Jul 2026 - **Updated:** 9 Jul 2026 - **Also known as:** CLEANSTART-2026-JI77146, CLEANSTART-2026-UE74978, CLEANSTART-2026-XE70573, DEBIAN-CVE-2026-59875, ECHO-717c-df78-ae50, GHSA-gvwx-54wh-qm9j, MINI-2hff-grhg-gq8x, MINI-3h53-2x5w-4hf4, MINI-3hpf-hrh5-x92f, MINI-3x32-2w5v-cmrp, MINI-4q5r-66p4-ppr3, MINI-53f6-rmrr-mq96, MINI-6g27-5648-mvh3, MINI-6mgx-j436-6g96, MINI-74h5-xg73-4phf, MINI-7qvv-wgxm-5r5g, MINI-7vpr-4j97-7w7j, MINI-9mpq-pj96-2f7r, MINI-9q45-8983-9w6q, MINI-c276-rw7j-5xwf, MINI-cmr3-hrm6-c883, MINI-f4g4-8hrm-9q5v, MINI-fgrf-792q-8rq5, MINI-fh6c-m696-4g2q, MINI-fq8p-fgjf-f7vx, MINI-hv35-f2x7-6x6g, MINI-j3cf-jr77-qfhm, MINI-jw5q-6x7v-3pv7, MINI-m45w-pw8c-wwm5, MINI-q83w-cvjh-g5cc, MINI-vcfp-5p49-cc78, MINI-vjwv-9pxj-5f4x, MINI-wc8r-c6r4-hh48, MINI-wfc8-mx5f-7hrr, MINI-wq4r-xp6c-q89w, MINI-wwfj-mp6x-6m5j, MINI-x5m2-794c-7vr3, ROOT-APP-NPM-CVE-2026-59875, UBUNTU-CVE-2026-59875 ## What is CVE-2026-59875? CVE-2026-59875 is a medium-severity denial of service vulnerability in isaacs node-tar, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.17, node-tar does not strip NUL bytes from PAX path and linkpath records in src/pax.ts, allowing a crafted archive with values to reach fs.lstat or fs.open and terminate the process with an uncaught exception. This issue is fixed in version 7.5.17. Weakness: CWE-248 (Uncaught Exception) ## Which versions are affected by CVE-2026-59875? 2 open source packages ship an affected version, including tar. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tar` | npm | All versions | 7.5.17 | | `tar` | npm | All versions | 7.5.17 | ## How do I fix CVE-2026-59875? Upgrade tar to 7.5.17 or later. ## Is CVE-2026-59875 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59875 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-59875 and fix it if it is affected. What it is: CVE-2026-59875 is a medium-severity denial of service vulnerability in isaacs node-tar, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59875 exists. Affected packages and fixed versions: - tar (npm): affected all versions; fixed in 7.5.17 - tar (npm): affected all versions; fixed in 7.5.17 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-59875/ (Markdown: https://insights.sbomify.com/CVE-2026-59875/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59875 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59875 - OSV: https://osv.dev/vulnerability/CVE-2026-59875 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-59875/ Summaries are generated and may contain mistakes; the official description above is the record.