{"answers":{"affected":"2 open source packages ship an affected version, including nanotar. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69874 exists.","fix":"No fix has been published for CVE-2025-69874 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69874 is a critical path traversal vulnerability in n/a, published on 11 Feb 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-2025-69874 and fix it if it is affected.\n\nWhat it is: CVE-2025-69874 is a critical path traversal vulnerability in n/a, published on 11 Feb 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-2025-69874 exists.\n\nAffected packages and fixed versions:\n- nanotar (npm): affected all versions up to 0.2.0; no fix listed\n- nanotar (npm): affected all versions up to 0.2.0; no fix listed\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-69874/ (Markdown: https://insights.sbomify.com/CVE-2025-69874/index.md)","id":"CVE-2025-69874","markdown":"https://insights.sbomify.com/CVE-2025-69874/index.md","name":"CVE-2025-69874","record":{"aliases":["GHSA-92fh-27vv-894w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"npm tar parsing library","requires_auth":"none","summary":"Remote attackers can write arbitrary files outside the intended directory via crafted tar archives in the nanotar library.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nanotar","vendor":"unjs"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"nanotar through 0.2.0 has a path traversal vulnerability in parseTar() and parseTarGzip() that allows remote attackers to write arbitrary files outside the intended extraction directory via a crafted tar archive containing path traversal sequence.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"nanotar is vulnerable to path traversal in parseTar() and parseTarGzip()","id":"CVE-2025-69874","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2025-69875"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nanotar","purl":null,"source":"GHSA-92fh-27vv-894w"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nanotar","purl":"pkg:npm/nanotar","source":"GHSA-92fh-27vv-894w"}],"prev":{"headline":"ajv has ReDoS when using `$data` option","id":"CVE-2025-69873"},"products":["n/a"],"published":"2026-02-11","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":"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-02-12","vendors":["n/a"]},"summary":"Remote attackers can write arbitrary files outside the intended directory via crafted tar archives in the nanotar library.","url":"https://insights.sbomify.com/CVE-2025-69874/"}