{"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-59871 exists.","fix":"Upgrade tar to 7.5.18 or later.","what":"CVE-2026-59871 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."},"fix_prompt":"Check this codebase for CVE-2026-59871 and fix it if it is affected.\n\nWhat it is: CVE-2026-59871 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59871 exists.\n\nAffected packages and fixed versions:\n- tar (npm): affected all versions; fixed in 7.5.18\n- tar (npm): affected all versions; fixed in 7.5.18\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-59871/ (Markdown: https://insights.sbomify.com/CVE-2026-59871/index.md)","id":"CVE-2026-59871","markdown":"https://insights.sbomify.com/CVE-2026-59871/index.md","name":"CVE-2026-59871","record":{"aliases":["CLEANSTART-2026-OD75176","CLEANSTART-2026-VH65256","CLEANSTART-2026-XO33315","DEBIAN-CVE-2026-59871","ECHO-6efb-ad73-64a1","GHSA-w8wr-v893-vjvp","MINI-28m8-q5vr-98g7","MINI-2g32-5c6m-8q3x","MINI-2gv9-9pjx-cxqh","MINI-2w48-h86f-3qf3","MINI-58r7-p626-5vx2","MINI-6466-849h-v5pf","MINI-66x9-57q8-g97h","MINI-69c9-c2mw-mrh5","MINI-8pv3-4fr4-pr8q","MINI-8qcg-5m2g-8qc4","MINI-93h9-xjf3-jph5","MINI-98ww-f952-cgf4","MINI-9mm4-fxhf-gpx4","MINI-9rj3-7wcj-3x2m","MINI-c4qv-c9cj-fp8m","MINI-f9vf-jp3j-jh23","MINI-g5px-r9w4-3rh6","MINI-hm6v-x4p3-5p7m","MINI-m8p7-mxg3-rwg2","MINI-p8j7-qfxq-q6jc","MINI-pxfm-7cr7-mhx2","MINI-pxhp-jw3f-7pfp","MINI-qc27-8cgh-2h9m","MINI-rg9x-q3x2-753v","MINI-v54f-vx62-597j","MINI-w5qj-v78h-c2v9","MINI-wf8x-69q9-px6g","MINI-whpj-g8gx-564h","MINI-wmj7-g333-rw67","MINI-x3w4-wp5w-4jr7","MINI-xf82-4wxr-pcvr","ROOT-APP-NPM-CVE-2026-59871","UBUNTU-CVE-2026-59871"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js tar library","requires_auth":"none","summary":"An attacker can crash the application by providing a tar archive with numeric PAX paths, causing an uncaught TypeError in the node-tar library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tar","vendor":"isaacs"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-704","name":"Incorrect Type Conversion or Cast"}],"description":"node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.18, node-tar coerces all-digit PAX path and linkpath values in src/pax.ts to JavaScript numbers, causing downstream path handling such as normalizeWindowsPath(entry.path).split('/') to throw an uncaught TypeError. This issue is fixed in version 7.5.18.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"node-tar: Process crash via PAX numeric path type confusion","id":"CVE-2026-59871","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"node-tar: Decompression/parse DoS via unlimited input","id":"CVE-2026-59873"},"packages":[{"ecosystem":"npm","fixed":["7.5.18"],"introduced":["0"],"last_affected":[],"package":"tar","purl":null,"source":"GHSA-w8wr-v893-vjvp"},{"ecosystem":"npm","fixed":["7.5.18"],"introduced":["0"],"last_affected":[],"package":"tar","purl":"pkg:npm/tar","source":"GHSA-w8wr-v893-vjvp"}],"prev":{"headline":"js-yaml quadratic-complexity denial of service via YAML11_SCHEMA !!omap parsing","id":"CVE-2026-59870"},"products":["node-tar"],"published":"2026-07-08","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-08","vendors":["isaacs"]},"summary":"An attacker can crash the application by providing a tar archive with numeric PAX paths, causing an uncaught TypeError in the node-tar library.","url":"https://insights.sbomify.com/CVE-2026-59871/"}