# CVE-2026-104854: Nx daemon and plugin worker sockets are accessible to other local users

> Local attackers can access Nx daemon sockets to execute code or read data due to insecure permissions and lack of authentication.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-w3vv-58gj-gw77, ROOT-APP-NPM-CVE-2026-104854

## What is CVE-2026-104854?

CVE-2026-104854 is a high-severity missing authorization vulnerability in nrwl nx, published on 2 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Nx is a monorepo solution for TypeScript and polyglot codebases. From 14.6.0 until 22.7.9 and 23.1.2, Nx creates Unix domain sockets for its daemon and isolated plugin workers in shared temporary locations without owner-only directory and socket permissions. Another unprivileged local account on a shared build server, developer host, or multi-user container can discover and connect to a running socket because the transport performs no authentication and relies on filesystem containment. The daemon's PROCESS_IN_BACKGROUND request accepts a module path and invokes its default export, allowing a caller that controls a file to execute code as the account running Nx; other handlers can expose workspace file contents, project graphs, and task hashes. Disabling the daemon alone does not remove the vulnerable plugin-worker sockets, while single-user machines without another local account are not exposed. This issue is fixed in versions 22.7.9 and 23.1.2.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-104854?

4 open source packages ship an affected version, including nx.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nx` | npm | From 14.6.0 | 22.7.9 |
| `nx` | npm | From 14.6.0 | 22.7.9 |
| `nx` | npm | From 23.0.0 | 23.1.2 |
| `nx` | npm | From 23.0.0 | 23.1.2 |

## How do I fix CVE-2026-104854?

Upgrade nx to a fixed version for your release line: 22.7.9 or 23.1.2.

## Is CVE-2026-104854 being exploited?

There is no known exploitation of CVE-2026-104854 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104854 and fix it if it is affected.

What it is: CVE-2026-104854 is a high-severity missing authorization vulnerability in nrwl nx, published on 2 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104854 in the wild and no public exploit code.

Affected packages and fixed versions:
- nx (npm): affected from 14.6.0; fixed in 22.7.9
- nx (npm): affected from 14.6.0; fixed in 22.7.9
- nx (npm): affected from 23.0.0; fixed in 23.1.2
- nx (npm): affected from 23.0.0; fixed in 23.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104854/ (Markdown: https://insights.sbomify.com/CVE-2026-104854/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104854
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104854
- OSV: https://osv.dev/vulnerability/CVE-2026-104854

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104854/
Summaries are generated and may contain mistakes; the official description above is the record.