Skip to content

Update dependency nx to v23.0.2 [SECURITY] - #29827

Open
tryghost-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-nx-vulnerability
Open

Update dependency nx to v23.0.2 [SECURITY]#29827
tryghost-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-nx-vulnerability

Conversation

@tryghost-renovate

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
nx (source) 23.0.123.0.2 age confidence

Nx: Zip-Slip in the self-hosted remote cache

CVE-2026-71476 / GHSA-vp3h-ghgh-jr7g

More information

Details

Summary

The Nx self-hosted HTTP remote cache extracts downloaded cache artifacts without constraining where files are written. A malicious — or on-path (MITM) — remote cache server can return a crafted tar archive whose entries escape the cache directory and write to arbitrary locations on the machine running Nx. This arbitrary file write can be escalated to remote code execution. The directly exploitable issue is the self-hosted HTTP remote cache.

Affected Packages

[!IMPORTANT]
Nx's default local cache and Nx Cloud are NOT affected. The default local cache and Nx Cloud use separate cache retrieval and extraction mechanisms that does not have this vulnerability. Only workspaces that use a self-hosted remote cache (NX_SELF_HOSTED_REMOTE_CACHE_SERVER, @nx/s3-cache, etc.) are affected.

Two self-hosted cache surfaces are affected:

  1. The built-in HTTP remote cache (NX_SELF_HOSTED_REMOTE_CACHE_SERVER, in nx) — fixed in the patched release.
  2. The self-hosted cache packages@nx/s3-cache, @nx/gcs-cache, @nx/azure-cache, @nx/shared-fs-cache (and their @nx/powerpack-* predecessors) — the same flaw in their own extractor. Deprecated (CVE-2025-36852) and not patched; migrate off (see Remediation).

The shared step that copies cached outputs into the workspace was also part of the exposure and is hardened in the patched nx release.

Remediation

Upgrade to Nx 22.7.7 or 23.0.2 (or later). The patched extractor is a drop-in — no configuration change is required.

If you use the S3, GCS, Azure, or shared-filesystem cache packages

@nx/s3-cache, @nx/gcs-cache, @nx/azure-cache, and @nx/shared-fs-cache (and their @nx/powerpack-* predecessors) are separately versioned packages and are already deprecated (see CVE-2025-36852). Upgrading nx hardens the shared restore step, but it does not fully secure these packages. The remediation for them is to migrate off — to Nx Cloud or the self-hosted OpenAPI/HTTP remote cache — per the deprecation guidance: https://nx.dev/docs/reference/deprecated/self-hosted-cache-packages

Details

When Nx retrieves an artifact from the self-hosted HTTP remote cache, it downloads a gzipped tar archive and extracts it. The extractor joined each untrusted tar entry name directly onto the output directory and unpacked it with tar's unguarded Entry::unpack(), which performs no containment check:

// vulnerable
let path_on_disk = output_dir.join(entry_path); // entry_path is attacker-controlled
fs::create_dir_all(path_on_disk.parent())?;
entry.unpack(&path_on_disk)?;

In addition, restore now copies only the declared task outputs (never the whole cache directory), confined to the workspace root; parent directories are realized as real directories so a write can never traverse a symlink; declared outputs that resolve outside the workspace are rejected; and the malformed-input cases return errors instead of panicking.

References
Credits
  • Lidor B., Novee Security — Reporter
  • Assaf Levkovich, Novee Security — Reporter

Severity

  • CVSS Score: 8.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

References

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


Release Notes

nrwl/nx (nx)

v23.0.2

Compare Source

23.0.2 (2026-07-10)

🚀 Features
  • core: re-add isCacheableTask helper (#​36177)
🩹 Fixes
  • bundling: prevent TS6059 when an app imports a workspace lib from source (#​36217, #​35017)
  • core: prefer module.registerHooks to avoid DEP0205 deprecation warning (#​36081)
  • core: prevent nx migrate crash when include=optional filters out the target package (#​36087)
  • core: make nx migrate honor preapproved packages and emit a valid temp workspace (#​36086)
  • core: skip daemon project-graph recompute on no-op file rewrites (#​36082)
  • core: prevent the TUI from auto-selecting a completed task when a batch finishes (#​35833)
  • core: deregister pseudo-terminal exit handlers when tasks finish (#​36115)
  • core: prevent path traversal / zip-slip in self-hosted remote cache (#​36116)
  • core: respect explicit --nxCloud=skip for AI agents in create-nx-workspace (#​36131)
  • core: warn when the self-hosted remote cache disables TLS verification (NXC-4593) (#​36132, #​36116)
  • core: throw actionable error when pnpm .modules.yaml is missing (#​35666, #​35635)
  • core: support ${configDir} in tsconfig path alias resolution (#​36037, #​35804)
  • core: prevent non-npm devEngines pin from breaking npm registry lookups (#​36020, #​35815)
  • core: clarify nx sync remediation messaging and surface spinner output in non-tty (#​35747)
  • core: exclude direct-dependency overrides from generated package.json (#​36040, #​35675)
  • core: apply target defaults when project.json overrides an inferred run-commands target with different commands (#​36142, #​36067)
  • core: run the nx.bat wrapper for dot-nx setup on windows (#​36048)
  • core: speed up bun lockfile parsing (#​36198)
  • core: set NX_CLI_SET in batch worker processes (#​36214, #​36210)
  • core: preserve comments in catalog YAML updates (#​35733)
  • core: box JsonFileSet payload to keep HashInstruction small (#​36247, #​35248, #​36244, #​36152)
  • core: share workspace fileset hash results instead of deep-cloning per task (#​36244, #​34971, #​34942)
  • core: replace per-input visited clones with undo-log scoping in hash planner (#​36248, #​35071, #​36152, #​34971, #​36244, #​35248, #​36247)
  • core: intern hash instructions in a pool and plan with id lists (#​36249, #​35071, #​36152, #​36248)
  • core: detect Codex sandbox on Linux to disable daemon and plugin isolation (#​36273)
  • devkit: restore prettier v2 support in formatFiles (#​36193)
  • graph: prevent project details web view top from being clipped (#​36154)
  • js: prevent doubled output paths in buildable library path mappings (#​36138, #​36079)
  • js: scope incremental type-check .tsbuildinfo per project (#​36137, #​36113)
  • js: preserve npm allowScripts allowlist in pruned package.json (#​36016, #​35931)
  • js: resolve catalog references in pruned package.json output (#​35805, #​35419)
  • js: avoid import locator unicode position panic (#​36133, #​36128)
  • js: prevent Windows TS6059 rootDir errors in tsc builds (#​36184, #​35696)
  • js: wait for process tree exit when stopping node executor tasks (#​36230)
  • linter: update terminal cli regex for local-dist build (#​36201, #​36199)
  • maven: de-flake maven e2e by dropping -X debug forks and widening timeout (#​36091)
  • misc: bump axios to 1.16.1 (#​36120)
  • misc: use default import for chalk in @​nx/workspace output.ts (#​35523, #​35521, #​34111, #​21201, #​26667)
  • misc: remove duplicate nx init cloud-prompt telemetry event (#​36145)
  • nx-cloud: use standard utm params on cloud prompt links (#​36227, #​36226)
  • nx-dev: remove empty SaaS and Mobile template filters (#​36085)
  • react: reserve ports in rspack e2e test to avoid default port collisions (#​36090)
  • react: stop pinning eslint-plugin-react in generated projects (#​36168, #​36161)
  • release: widen release e2e timeouts to absorb pre-version dlx install (#​36092)
  • repo: trust wix/brew tap so macOS detox CI can install applesimutils (#​36146)
  • rspack: use contenthash for chunkFilename to prevent stale chunks (#​36136, #​2292, #​36014)
  • rspack: stop mocking non-existent is-serve-mode util in apply-base-config test (fea2cabbcc)
  • vite: widen vite ts-solution e2e build timeouts for cold multi-lib build (#​36093)
  • vite: detect @​vitejs/plugin-vue2 (vite:vue2) for vue-tsc typecheck (#​36125, #​36094)
  • vite: update deprecation docs link (#​36070, #​36053)
  • vitest: support passing mode through to vitest (#​35069)
  • web: run executor/plugin/generator commands with the workspace package manager (#​36021, #​35950)
  • webpack: prevent TS6059 when a tsc build bundles a workspace lib (#​36188, #​35017)
❤️ Thank You

Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Only on Sunday and Saturday (* * * * 0,6)
    • Between 11:00 PM and 11:59 PM, Monday through Friday (* 23 * * 1-5)
    • Between 12:00 AM and 04:59 AM, Monday through Saturday (* 0-4 * * 1-6)

🚦 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 has been generated by Mend Renovate.

@tryghost-renovate tryghost-renovate Bot added dependencies Pull requests that update a dependency file security labels Aug 7, 2026
@tryghost-renovate

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined
Post-upgrade command 'pnpm install --no-frozen-lockfile --filter @internal/scripts --prod --ignore-scripts' has not been added to the allowed list in allowedCommands
File name: undefined
Post-upgrade command 'node scripts/generate-changeset.js' has not been added to the allowed list in allowedCommands

@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch from 5cbaf8e to d50208d Compare August 7, 2026 23:33
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 7, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 7, 2026
@tryghost-renovate
tryghost-renovate Bot deleted the renovate/npm-nx-vulnerability branch August 7, 2026 23:38
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 8, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch 2 times, most recently from d50208d to 4490516 Compare August 8, 2026 00:36
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 8, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch 2 times, most recently from 4490516 to 1ac44dd Compare August 8, 2026 03:00
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 8, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch 2 times, most recently from 1ac44dd to 6d44548 Compare August 8, 2026 04:41
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 8, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch 3 times, most recently from 44d9a81 to ed963e0 Compare August 8, 2026 10:32
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 8, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch 2 times, most recently from a0889c9 to 0be347f Compare August 8, 2026 20:31
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 8, 2026
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 9, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch 2 times, most recently from 0be347f to 08ef583 Compare August 9, 2026 00:38
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 9, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch 2 times, most recently from 08ef583 to 4244e5a Compare August 9, 2026 04:47
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 9, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch 2 times, most recently from 4244e5a to fe9d123 Compare August 9, 2026 08:33
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] Update dependency nx to v23.0.2 [SECURITY] - autoclosed Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot closed this Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot changed the title Update dependency nx to v23.0.2 [SECURITY] - autoclosed Update dependency nx to v23.0.2 [SECURITY] Aug 9, 2026
@tryghost-renovate tryghost-renovate Bot reopened this Aug 9, 2026
@tryghost-renovate
tryghost-renovate Bot force-pushed the renovate/npm-nx-vulnerability branch from fb602de to fe9d123 Compare August 9, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants