VulnerabilityPublished 6 Oct 2026Updated 29 Oct 2026

CVE-2026-104853: Path traversal in nx migrate package-migrations extraction

Affects nxSource GCVE Database

Compare

Authoritative record:CVE-2026-104853· Medium 5.8

Not known to be exploited · CVSS 5.8 Medium : upgrade to 23.2.1 when convenient.

Data as of 30 Oct 2026, 08:15 UTC

CVSS 4.0 base score

5.8Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 23.2.1

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

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: High
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade nx to 23.2.1.

Affected software

Product	Affected	Fixed in
Homebrewnx`pkg:brew/nx`Other threats	Affected >=21.0.4 <23.2.1	Fixed in 23.2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you run `nx migrate` normally, no action is required because it fetches and runs the latest patched nx version. Upgrade to nx version 22.7.10 or later (22.x line) or 23.2.1 or later (23.x line) if you bypass the default hand-off to the latest nx version by setting environment variables such as `NX_USE_LOCAL` or `NX_MIGRATE_USE_LOCAL`, pinning `NX_MIGRATE_CLI_VERSION` to a vulnerable version, resuming with `--run-id`, or if fallback to the local nx occurs. Avoid running `nx migrate` against untrusted packages or package groups. The fix is a drop-in and does not require configuration changes.

Description

CVE-2026-104853 is a path traversal vulnerability in the nx tool's migrate command. It occurs because the migration file path from a package manifest is not validated, allowing extraction outside the intended temporary directory. This can lead to attacker-controlled file writes or truncation of files writable by the user, potentially enabling code execution if critical files are overwritten. The vulnerability affects nx versions from 13.10.0 up to but not including 22.7.10, and from 23.0.0 up to but not including 23.2.1. Most users running nx migrate normally are not exposed because the tool fetches and runs the latest patched nx version. Exposure occurs only if the local vulnerable nx version is forced to run. A fix is available in versions 22.7.10 and 23.2.1. No known exploitation in the wild has been reported.

Impact

An attacker controlling a package or a package transitively included via a trusted package can cause arbitrary file writes or truncation during migration planning. This can overwrite critical files such as shell configuration files, git hooks, or CI scripts, potentially leading to code execution with the privileges of the user running `nx migrate`. The vulnerability does not require user approval or execution of migrations to be exploited. However, exploitation requires the victim to run `nx migrate` against a malicious package while bypassing the default behavior of running the latest nx version.

Summary

`nx migrate` reads the `nx-migrations.migrations` path from package manifests and extracts migration files to a temporary directory. The path value is not validated and can contain `..` segments or absolute paths, enabling extraction outside the temporary directory. This allows a malicious package or any package transitively included via a trusted package's `packageGroup` to write attacker-controlled content or truncate files anywhere writable by the user. The vulnerability occurs during migration planning before user approval or execution of migrations. By default, `nx migrate` runs the latest nx version installed temporarily, which is patched; the vulnerability is only exposed if the local vulnerable nx version is forced to run (e.g., via environment variables or fallback). Affected versions are >=13.10.0 and <22.7.10, and >=23.0.0 and <23.2.1. The fix in 22.7.10 and 23.2.1 ensures proper path handling and validation. No evidence of exploitation in the wild exists.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 08:15 UTC

Technical details

References

Community reviews

Related threats