{"answers":{"affected":"6 open source packages ship an affected version, including tar-fs.","exploited":"There is no known exploitation of CVE-2025-59343 in the wild and no public exploit code.","fix":"Upgrade tar-fs to a fixed version for your release line: 1.16.6, 2.1.4 or 3.1.1.","what":"CVE-2025-59343 is a high-severity path traversal vulnerability in mafintosh tar-fs, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59343 and fix it if it is affected.\n\nWhat it is: CVE-2025-59343 is a high-severity path traversal vulnerability in mafintosh tar-fs, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59343 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tar-fs (npm): affected all versions; fixed in 1.16.6\n- tar-fs (npm): affected all versions; fixed in 1.16.6\n- tar-fs (npm): affected from 2.0.0; fixed in 2.1.4\n- tar-fs (npm): affected from 2.0.0; fixed in 2.1.4\n- tar-fs (npm): affected from 3.0.0; fixed in 3.1.1\n- tar-fs (npm): affected from 3.0.0; fixed in 3.1.1\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-2025-59343/ (Markdown: https://insights.sbomify.com/CVE-2025-59343/index.md)","id":"CVE-2025-59343","markdown":"https://insights.sbomify.com/CVE-2025-59343/index.md","name":"CVE-2025-59343","record":{"aliases":["DEBIAN-CVE-2025-59343","DLA-4313-1","DSA-6013-1","ECHO-2e8d-40a9-3ad3","GHSA-vj76-c3g6-qr5v","MINI-3cj6-3x8r-r2rj","MINI-6r28-h7r5-734v","MINI-83pf-7m4p-gr7m","MINI-fv4c-p4wp-f8fp","MINI-g5cv-jmh4-g7mm","MINI-j469-vjhp-559p","MINI-jv83-f4gq-5pxv","MINI-vf3j-q8fv-h8vx","MINI-vfg4-9fp4-84x2","MINI-vjvx-rvcv-jhp6","ROOT-APP-NPM-CVE-2025-59343","UBUNTU-CVE-2025-59343"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js tar library","requires_auth":"none","summary":"Attackers can bypass symlink validation in tar-fs to write files outside the intended directory if the destination path is predictable.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"tar-fs provides filesystem bindings for tar-stream. Versions prior to 3.1.1, 2.1.3, and 1.16.5 are vulnerable to symlink validation bypass if the destination directory is predictable with a specific tarball. This issue has been patched in version 3.1.1, 2.1.4, and 1.16.6. A workaround involves using the ignore option on non files/directories.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"tar-fs has a symlink validation bypass if destination directory is predictable with a specific tarball","id":"CVE-2025-59343","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":6,"n_references":2,"next":{"headline":"AliasVault Vulnerable to Server-Side Request Forgery via Favicon Extraction","id":"CVE-2025-59344"},"packages":[{"ecosystem":"npm","fixed":["1.16.6"],"introduced":["0"],"last_affected":[],"package":"tar-fs","purl":null,"source":"GHSA-vj76-c3g6-qr5v"},{"ecosystem":"npm","fixed":["1.16.6"],"introduced":["0"],"last_affected":[],"package":"tar-fs","purl":"pkg:npm/tar-fs","source":"GHSA-vj76-c3g6-qr5v"},{"ecosystem":"npm","fixed":["2.1.4"],"introduced":["2.0.0"],"last_affected":[],"package":"tar-fs","purl":null,"source":"GHSA-vj76-c3g6-qr5v"},{"ecosystem":"npm","fixed":["2.1.4"],"introduced":["2.0.0"],"last_affected":[],"package":"tar-fs","purl":"pkg:npm/tar-fs","source":"GHSA-vj76-c3g6-qr5v"},{"ecosystem":"npm","fixed":["3.1.1"],"introduced":["3.0.0"],"last_affected":[],"package":"tar-fs","purl":null,"source":"GHSA-vj76-c3g6-qr5v"},{"ecosystem":"npm","fixed":["3.1.1"],"introduced":["3.0.0"],"last_affected":[],"package":"tar-fs","purl":"pkg:npm/tar-fs","source":"GHSA-vj76-c3g6-qr5v"}],"prev":{"headline":"esm.sh writes arbitrary files via path traversal in `X-Zone-Id` header","id":"CVE-2025-59342"},"products":["tar-fs"],"published":"2025-09-24","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["mafintosh"]},"summary":"Attackers can bypass symlink validation in tar-fs to write files outside the intended directory if the destination path is predictable.","url":"https://insights.sbomify.com/CVE-2025-59343/"}