Privilege Escalation in nx (CVE-2026-104854)
Summary
Vulnerability in nx (CVE-2026-104854). Risk of unauthorized operations or information disclosure. Exploitable via PROCESS_IN_BACKGROUND. Mitigation: upgrade to 23.1.2 or later.
Original description
The description as published by the source.
Summary
Nx creates the Unix domain sockets for its daemon and its plugin workers in a shared temporary directory with default permissions, so any other user on the same machine can connect to them. The daemon accepts a PROCESS_IN_BACKGROUND request that names a module to load and invokes its default export, which turns socket access into code execution inside the daemon process. On a multi-user machine — a shared build server, a shared developer box, or a container running several accounts — one local user can execute code as another user running Nx.
Severity
Exploitable by any other unprivileged local user on a shared host while a daemon or plugin worker is running, with no user interaction. There is no known evidence of exploitation in the wild.
Affected & Patched Versions
| Package | Vulnerable | Patched |
|---|---|---|
nx |
>= 14.6.0, < 22.7.9; >= 23.0.0, < 23.1.2 |
22.7.9, 23.1.2 |
Every version in the ranges above is affected. The lower bound is 14.6.0, when the daemon request handler that turns socket access into code execution was added.
[!IMPORTANT]
Single-user machines are not exposed. The vulnerability requires another local account on the same host, so an ordinary laptop with one user account is unaffected — the exposure is shared CI runners, shared build and development servers, and containers or images that run more than one uid.Disabling the daemon is not sufficient on its own: the plugin worker sockets used by plugi…
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-104854 has been found in nx.
Attackers can target a specific entry point like PROCESS_IN_BACKGROUND over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nx to 23.1.2 or later.
If unsure, ask your IT team or search "nx CVE-2026-104854" on the vendor's site.
CVE-2026-104854 (nx) — CWE-269
Attack surface: PROCESS_IN_BACKGROUND / NX_SOCKET_DIR
Patched: 23.1.2 — 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.
A vulnerability (CWE-269) exists in nx. Attackers reach the vulnerable code path via PROCESS_IN_BACKGROUND.
Check the vendor advisory for the affected versions of nx. Attack surface: PROCESS_IN_BACKGROUND / NX_SOCKET_DIR.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 23.1.2.
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.1.2ステージング環境で 23.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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