{"answers":{"affected":"2 open source packages ship an affected version, including zx.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13437 exists.","fix":"Upgrade zx to 8.8.5 or later.","what":"CVE-2025-13437 is a medium-severity path traversal vulnerability in Google zx, published on 20 Nov 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-13437 and fix it if it is affected.\n\nWhat it is: CVE-2025-13437 is a medium-severity path traversal vulnerability in Google zx, published on 20 Nov 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-13437 exists.\n\nAffected packages and fixed versions:\n- zx (npm): affected all versions; fixed in 8.8.5\n- zx (npm): affected all versions; fixed in 8.8.5\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-13437/ (Markdown: https://insights.sbomify.com/CVE-2025-13437/index.md)","id":"CVE-2025-13437","markdown":"https://insights.sbomify.com/CVE-2025-13437/index.md","name":"CVE-2025-13437","record":{"aliases":["GHSA-w87r-vg9q-crqm"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Google zx CLI","requires_auth":"none","summary":"Attackers can delete arbitrary external node_modules directories by exploiting a symlink cleanup logic error in the Google zx CLI when using the --prefer-local flag.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:U","version":"4.0"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"description":"When zx is invoked with --prefer-local=\u003cpath\u003e, the CLI creates a symlink named ./node_modules pointing to \u003cpath\u003e/node_modules. Due to a logic error in src/cli.ts (linkNodeModules / cleanup), the function returns the target path instead of the alias (symlink path). The later cleanup routine removes what it received, which deletes the target directory itself. Result: zx can delete an external \u003cpath\u003e/node_modules outside the current working directory.","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":"Arbitrary node_modules Directory Deletion in Google zx","id":"CVE-2025-13437","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Page Title, Description \u0026 Open Graph Updater \u003c= 1.02 - Cross-Site Request Forgery to Arbitrary Page Title Modification","id":"CVE-2025-13438"},"packages":[{"ecosystem":"npm","fixed":["8.8.5"],"introduced":["0"],"last_affected":[],"package":"zx","purl":null,"source":"GHSA-w87r-vg9q-crqm"},{"ecosystem":"npm","fixed":["8.8.5"],"introduced":["0"],"last_affected":[],"package":"zx","purl":"pkg:npm/zx","source":"GHSA-w87r-vg9q-crqm"}],"prev":{"headline":"Allocation of Resources Without Limits or Throttling in GitLab","id":"CVE-2025-13436"},"products":["zx"],"published":"2025-11-20","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-11-20","vendors":["Google"]},"summary":"Attackers can delete arbitrary external node_modules directories by exploiting a symlink cleanup logic error in the Google zx CLI when using the --prefer-local flag.","url":"https://insights.sbomify.com/CVE-2025-13437/"}