{"answers":{"affected":"2 open source packages ship an affected version, including tar.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64118 exists.","fix":"Upgrade tar to 7.5.2 or later.","what":"CVE-2025-64118 is a medium-severity vulnerability in isaacs node-tar, published on 30 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-64118 and fix it if it is affected.\n\nWhat it is: CVE-2025-64118 is a medium-severity vulnerability in isaacs node-tar, published on 30 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64118 exists.\n\nAffected packages and fixed versions:\n- tar (npm): affected from 7.5.1; fixed in 7.5.2\n- tar (npm): affected from 7.5.1; fixed in 7.5.2\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-64118/ (Markdown: https://insights.sbomify.com/CVE-2025-64118/index.md)","id":"CVE-2025-64118","markdown":"https://insights.sbomify.com/CVE-2025-64118/index.md","name":"CVE-2025-64118","record":{"aliases":["GHSA-29xp-372q-xqph","MINI-6wvx-vq4h-6vg8","MINI-9wr8-2m24-p869","MINI-fgph-r2jc-jxrw","MINI-j7fc-35j5-h4j9","MINI-m9p4-37x3-gp35","MINI-v8p3-9rjm-vqcg","MINI-xmqj-6j9x-hh8f","ROOT-APP-NPM-CVE-2025-64118","UBUNTU-CVE-2025-64118"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Node.js tar library","requires_auth":"low_privilege","summary":"An attacker can expose uninitialized memory by shrinking a tar file on disk during synchronous list operations in node-tar.","user_interaction":"required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:L/VA:L/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"node-tar is a Tar for Node.js. In 7.5.1, using .t (aka .list) with { sync: true } to read tar entry contents returns uninitialized memory contents if tar file was changed on disk to a smaller size while being read. This vulnerability is fixed in 7.5.2.","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 vulnerable to race condition leading to uninitialized memory exposure","id":"CVE-2025-64118","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":2,"n_references":4,"next":{"headline":"Nuvation Energy BMS Client-side Authentication","id":"CVE-2025-64119"},"packages":[{"ecosystem":"npm","fixed":["7.5.2"],"introduced":["7.5.1"],"last_affected":[],"package":"tar","purl":null,"source":"GHSA-29xp-372q-xqph"},{"ecosystem":"npm","fixed":["7.5.2"],"introduced":["7.5.1"],"last_affected":[],"package":"tar","purl":"pkg:npm/tar","source":"GHSA-29xp-372q-xqph"}],"prev":{"headline":"Tuleap missing CSRF protection in the management of SVN commit rules and immutable tags","id":"CVE-2025-64117"},"products":["node-tar"],"published":"2025-10-30","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-30","vendors":["isaacs"]},"summary":"An attacker can expose uninitialized memory by shrinking a tar file on disk during synchronous list operations in node-tar.","url":"https://insights.sbomify.com/CVE-2025-64118/"}