Path Traversal in nx (CVE-2026-104853)
Summary
Path traversal in nx (CVE-2026-104853). Risk of unauthorized operations or information disclosure. Exploitable via migrations. Mitigation: upgrade to 23.2.1 or later.
Original description
The description as published by the source.
Summary
nx migrate reads each target package's nx-migrations.migrations value from its manifest and extracts the referenced file to a path built by joining that value onto a temporary directory. The value is never validated, so a package whose migrations field contains .. segments (or an absolute path) steers the extraction to write outside the temporary directory. A hostile package — or any package pulled in transitively through a trusted package's packageGroup — can write attacker-controlled content, or truncate an existing file, anywhere the running user can write. This happens during migration planning, before the user reviews the migration list and before --run-migrations, so it does not require the user to approve or execute anything.
Most workspaces need no action. By default nx migrate does not run the nx installed in your workspace — it installs nx@latest into a temporary directory and performs the upgrade planning, including this extraction, with that copy. Now that a patched nx is the latest release, a default nx migrate run is unaffected whatever version the workspace has installed. The installed version only runs, and is only then exposed, when that hand-off is bypassed — see Remediation.
Severity
Exploitable when the victim runs nx migrate against a package the attacker controls, directly or through a trusted package's packageGroup. The primary impact is a file write with attacker-controlled content and no path confinement;…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-104853 has been found in nx.
Attackers can target a specific entry point like migrations over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nx to 23.2.1 or later.
If unsure, ask your IT team or search "nx CVE-2026-104853" on the vendor's site.
CVE-2026-104853 (nx) — CWE-22
Attack surface: migrations / packageGroup / NX_USE_LOCAL / NX_MIGRATE_USE_LOCAL
Patched: 23.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in nx. Attackers reach the vulnerable code path via migrations.
Check the vendor advisory for the affected versions of nx. Attack surface: migrations / packageGroup / NX_USE_LOCAL / NX_MIGRATE_USE_LOCAL.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 23.2.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nx' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nx' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nxを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade nx to 23.2.1ステージング環境で 23.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com