Update Nx packages to v23.2.1 [SECURITY]

[renovate]

Updates both nx and @nx/js to 23.2.1 so the workspace does not retain the vulnerable transitive Nx 23.2.0 copy. The new Nx postinstall remains explicitly disabled; Nx runs using its prebuilt platform package.

Validation: frozen pnpm install, format check, lint, and all 42 package test targets pass locally.

---

This PR contains the following updates:

Package	Change	Age	Confidence
nx (source)	23.2.0 → 23.2.1

---

Nx: Path traversal in nx migrate package-migrations extraction

CVE-2026-104853 / GHSA-hrvq-x7jp-36xv

More information

Details

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; overwriting an auto-loaded file (a shell rc, a git hook, a CI script) escalates that write to code execution. There is no known evidence of exploitation in the wild.

Affected & Patched Versions

Package	Vulnerable	Patched
nx	>= 13.10.0, < 22.7.10; >= 23.0.0, < 23.2.1	22.7.10, 23.2.1

Every version in the ranges above is affected. The lower bound is 13.10.0, the first release where nx migrate extracted a package's migrations file from its tarball; earlier versions resolved migrations without that extraction.

[!IMPORTANT]
nx migrate normally fetches and runs nx@latest rather than the nx installed in your workspace. The ranges above therefore say where the vulnerable code ships, not who is exposed — it only runs when that hand-off is bypassed.

Remediation

If you run nx migrate normally, there is nothing to do. It resolves and runs the latest nx, which is patched, so your workspace's own nx version does not matter for this flaw.

Upgrade only if you bypass that hand-off and run the workspace's nx instead — that is, if you set NX_USE_LOCAL or NX_MIGRATE_USE_LOCAL, pin NX_MIGRATE_CLI_VERSION to an affected version, resume an existing run with --run-id, or run where the temporary install fails and nx migrate falls back to the local nx. In those cases upgrade to 22.7.10 (22.x line) or 23.2.1 (23.x line) or later:

nx migrate 23.2.1

The fix is a drop-in — no configuration changes are required, and no legitimate migrations value is affected (real packages reference ./migrations.json or another path within their own directory, all of which remain valid). Either way, do not run nx migrate against packages, or packageGroup members, that you do not trust.

Details

While planning an upgrade, nx migrate extracts each target package's migrations file to a destination built by joining the package's own nx-migrations.migrations value onto a temporary directory. That value is read from the manifest without validation, and it is handled asymmetrically: the name Nx matches against the archive entries is normalized (so its .. segments collapse), while the destination path it writes to is a raw join that keeps the .. segments and resolves outside the temporary directory. Because the attacker controls the tarball, they name their entry to equal the normalized form; the match then succeeds and the bytes are written to the un-normalized, escaping destination. The normalization is not a defence — it only dictates what the attacker must name their entry.

The same value also seeds the directory used for prompt-file extraction, which has the same shape, so both writes are steerable from the one field.

Two distinct primitives fall out of this:

• Truncation — the destination write stream is opened, and truncates, before any tar entry is inspected. So a package that points migrations at an existing file empties that file even when no tar entry matches — no crafted archive required.
• Controlled write — when a tar entry's name matches, its bytes are written to the escaping destination. The extractor performs no path containment of its own.

Credits

• Arkadiusz Marta (RE:SOURCE) — Reporter

Severity

• CVSS Score: 5.8 / 10 (Medium)
• Vector String: 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

References

• https://github.com/nrwl/nx/security/advisories/GHSA-hrvq-x7jp-36xv
• https://nvd.nist.gov/vuln/detail/CVE-2026-104853
• https://github.com/nrwl/nx/pull/36887
• https://github.com/nrwl/nx/commit/38cd82a0c05e8212e538bdb87ccb198d6504e58f
• https://github.com/nrwl/nx/commit/95474ab457e8e1dbdbefad29040c166105a8fb90
• https://github.com/nrwl/nx/commit/de37c5ebd1852fac700d70726326236ac398af3f
• https://github.com/nrwl/nx/releases/tag/22.7.10
• https://github.com/nrwl/nx/releases/tag/23.2.1
• https://github.com/advisories/GHSA-hrvq-x7jp-36xv

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nrwl/nx (nx)

v23.2.1

Compare Source

23.2.1 (2026-09-09)

🚀 Features

• core: report the cache location alongside usage (#​36959)
• repo: add a .NET example for @​nx/dotnet (#​36701)

🩹 Fixes

• angular: correct declaration maps and exports of buildable libraries (#​36373, #​36357)
• core: separate daemon runtime env from graph identity (#​36565, #​36564)
• core: validate the migrations path before extracting package migrations (#​36887)
• core: release per-run process listeners and task history results (#​36866)
• core: read the pnpm 12 min-release-age policy instead of deferring to an install (#​36915, #​36914)
• core: carry minimumReleaseAge into pruned pnpm deploy output (#​36900, #​36899)
• core: report how a plugin worker was lost instead of always calling it an exit (#​36894)
• core: keep the cache in the workspace on CI (#​36922)
• core: restore the wasm walker imports dropped by a stray cfg attribute (#​36924)
• core: avoid mutating target options when resolving configurations (#​36934)
• js: resolve tsconfig to absolute path so ${configDir} paths type-check without baseUrl (#​36445)
• misc: scan package projects for env vars (#​36847)
• release: exclude AI coding agents from the changelog Thank You section (#​36892)
• release: use the release group name when resolving the previous tag for fixed groups (#​36554)
• repo: provision JDK 17 for Gradle builds with mise (#​36965)
• repo: guard JAVA17_HOME against an uninstalled JDK (#​36969)
• rspack: write the normalized cache option in NxAppRspackPlugin (#​36905, #​36878)

❤️ Thank You

• AgentEnder @​AgentEnder
• Caleb Ukle
• Claude
• Craigory Coppola @​AgentEnder
• Denis Frenademetz @​skrtheboss
• Eduardo Speroni @​edusperoni
• Federico Bartoli
• FrozenPandaz @​FrozenPandaz
• Jack Stevenson
• Jason Jean @​FrozenPandaz
• Jupiter Jayna @​sdjayna
• Juri Strumpflohner @​juristr
• Leosvel Pérez Espinosa @​leosvelperez
• Nicolas Beaussart @​beaussan
• ShwethaSundar
• Stephen Jayna

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: ecaf1165-84af-4daf-a5ed-9e57fad9bda5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.82%. Comparing base (f7ff4d8) to head (e061017).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1036   +/-   ##
=======================================
  Coverage   97.82%   97.82%           
=======================================
  Files          92       92           
  Lines        3133     3133           
  Branches      554      554           
=======================================
  Hits         3065     3065           
  Misses         24       24           
  Partials       44       44           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.