{"answers":{"affected":"4 open source packages ship an affected version, including nx.","exploited":"There is no known exploitation of CVE-2026-104853 in the wild and no public exploit code.","fix":"Upgrade nx to a fixed version for your release line: 22.7.10 or 23.2.1.","what":"CVE-2026-104853 is a medium-severity path traversal vulnerability in nrwl nx, published on 2 Oct 2026. 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-2026-104853 and fix it if it is affected.\n\nWhat it is: CVE-2026-104853 is a medium-severity path traversal vulnerability in nrwl nx, published on 2 Oct 2026. 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: There is no known exploitation of CVE-2026-104853 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nx (npm): affected from 13.10.0; fixed in 22.7.10\n- nx (npm): affected from 13.10.0; fixed in 22.7.10\n- nx (npm): affected from 23.0.0; fixed in 23.2.1\n- nx (npm): affected from 23.0.0; fixed in 23.2.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-2026-104853/ (Markdown: https://insights.sbomify.com/CVE-2026-104853/index.md)","id":"CVE-2026-104853","markdown":"https://insights.sbomify.com/CVE-2026-104853/index.md","name":"CVE-2026-104853","record":{"aliases":["GHSA-hrvq-x7jp-36xv"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Nx monorepo tool","requires_auth":"none","summary":"Attackers can write arbitrary files outside the temporary directory during Nx migration planning, potentially leading to code execution or data modification.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Nx is a monorepo solution for TypeScript and polyglot codebases. From 13.10.0 until 22.7.10 and 23.2.1, Nx migration planning reads the nx-migrations.migrations value from a target package manifest without validating that it is a contained relative path. A hostile direct dependency or a package introduced through a trusted package's packageGroup can supply .. segments or an absolute path, causing nx migrate to join an escaping destination onto its temporary directory. The migration archive can then write attacker-controlled bytes outside the temporary directory, while opening the destination stream can truncate an existing writable file even when no archive entry matches. This occurs during migration planning before review of the migration list or use of --run-migrations; the vulnerable installed Nx copy is reached when the normal nx@latest handoff is bypassed with NX_USE_LOCAL, NX_MIGRATE_USE_LOCAL, NX_MIGRATE_CLI_VERSION, --run-id, or fallback after a temporary-install failure. This issue is fixed in versions 22.7.10 and 23.2.1.","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":"Nx: Path traversal in nx migrate package-migrations extraction","id":"CVE-2026-104853","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":4,"n_references":7,"next":{"headline":"Nx daemon and plugin worker sockets are accessible to other local users","id":"CVE-2026-104854"},"packages":[{"ecosystem":"npm","fixed":["22.7.10"],"introduced":["13.10.0"],"last_affected":[],"package":"nx","purl":null,"source":"GHSA-hrvq-x7jp-36xv"},{"ecosystem":"npm","fixed":["22.7.10"],"introduced":["13.10.0"],"last_affected":[],"package":"nx","purl":"pkg:npm/nx","source":"GHSA-hrvq-x7jp-36xv"},{"ecosystem":"npm","fixed":["23.2.1"],"introduced":["23.0.0"],"last_affected":[],"package":"nx","purl":null,"source":"GHSA-hrvq-x7jp-36xv"},{"ecosystem":"npm","fixed":["23.2.1"],"introduced":["23.0.0"],"last_affected":[],"package":"nx","purl":"pkg:npm/nx","source":"GHSA-hrvq-x7jp-36xv"}],"prev":{"headline":"GraphQL Tools has prototype pollution in well-established utility function `mergeDeep`","id":"CVE-2026-104852"},"products":["nx"],"published":"2026-10-02","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":"2026-10-02","vendors":["nrwl"]},"summary":"Attackers can write arbitrary files outside the temporary directory during Nx migration planning, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/CVE-2026-104853/"}