Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.8amended

Nx: Path traversal in nx migrate package-migrations extraction

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nx 23.2.1, 22.7.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm nx

    Affected
    >= 13.10.0, < 22.7.10>= 23.0.0, < 23.2.1
    Fixed in
    23.2.1, 22.7.10

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.8 · 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 · score source
EPSS
  • CVE-2026-104853: 0.17% estimated exploitation activity in the next 30 days; percentile 6.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-hrvq-x7jp-36xv

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-hrvq-x7jp-36xv

  4. Revision 1 · created ·

    Published from ghsa record GHSA-hrvq-x7jp-36xv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-104853

Advisory: Nx: Path traversal in nx migrate package-migrations extraction
IDs: CVE-2026-104853, GHSA-hrvq-x7jp-36xv
Record: https://patchnext.com/advisories/cve-2026-104853 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nx 23.2.1, 22.7.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nx: affected >= 13.10.0, < 22.7.10; >= 23.0.0, < 23.2.1; fixed in 23.2.1, 22.7.10

## Suggested inspection (read-only)
- `npm ls nx --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nx.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hrvq-x7jp-36xv (GitHub-reviewed advisory GHSA-hrvq-x7jp-36xv lists affected ranges: npm nx >=13.10.0 =23.0.0 <23.2.1)
- Verified: https://osv.dev/vulnerability/GHSA-hrvq-x7jp-36xv (OSV record GHSA-hrvq-x7jp-36xv lists affected ranges: npm nx >=13.10.0 =23.0.0 <23.2.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…