# CVE-2026-56301: Nuxt - Arbitrary File Read via World-Connectable vite-node IPC Socket on Linux

> Local attackers can read arbitrary files via an unprotected IPC socket in the Nuxt development server on Linux.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-534h-c3cw-v3h9

## What is CVE-2026-56301?

CVE-2026-56301 is a medium-severity path traversal vulnerability in Nuxt, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Nuxt 4.0.0 before 4.4.7 and 3.18.0 before 3.21.7, when running the development server (nuxt dev) on Linux, binds the vite-node IPC server to an abstract-namespace Unix socket without permission restrictions, allowing local users to enumerate and connect. Unprivileged co-resident users can exploit the unprotected module request handler to read arbitrary files such as .env and SSH keys through the SSR plugin pipeline. Production builds are unaffected, as the IPC server runs only in development.

Weakness: CWE-276 (Incorrect Default Permissions)

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

4 open source packages ship an affected version, including nuxt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt` | npm | From 3.18.0 | 3.21.7 |
| `nuxt` | npm | From 3.18.0 | 3.21.7 |
| `nuxt` | npm | From 4.0.0 | 4.4.7 |
| `nuxt` | npm | From 4.0.0 | 4.4.7 |

Products: Nuxt Nuxt.

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

Upgrade nuxt to a fixed version for your release line: 3.21.7 or 4.4.7.

## Is CVE-2026-56301 being exploited?

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

## Other vulnerabilities in Nuxt

- [CVE-2026-53721](https://insights.sbomify.com/CVE-2026-53721/): Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher (high 8.8)
- [CVE-2024-23657](https://insights.sbomify.com/CVE-2024-23657/): Path Traversal: '../filedir' in Nuxt Devtools (high 8.8)
- [CVE-2024-34344](https://insights.sbomify.com/CVE-2024-34344/): Remote code execution via the browser when running the test locally in nuxt (high 8.8)
- [CVE-2024-42352](https://insights.sbomify.com/CVE-2024-42352/): Server-Side Request Forgery (SSRF) in nuxt-icon (high 8.6)
- [CVE-2023-3224](https://insights.sbomify.com/CVE-2023-3224/): Code Injection in nuxt/nuxt (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56301 is a medium-severity path traversal vulnerability in Nuxt, published on 23 Jun 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-56301 in the wild and no public exploit code.

Affected packages and fixed versions:
- nuxt (npm): affected from 3.18.0; fixed in 3.21.7
- nuxt (npm): affected from 3.18.0; fixed in 3.21.7
- nuxt (npm): affected from 4.0.0; fixed in 4.4.7
- nuxt (npm): affected from 4.0.0; fixed in 4.4.7

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-56301/ (Markdown: https://insights.sbomify.com/CVE-2026-56301/index.md)
```

## Sources

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

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