Vulnerabilities in pkg:npm/nuxt
PACKAGECVE-2026-56301 is a MODERATE (CVSS 5.5) nuxt dev server vite-node ipc vulnerability (CWE-276: Incorrect Default Permissions) affecting Nuxt libraries in the npm ecosystem. The issue involves nuxt dev server vite-node ipc socket is world-connectable on linux. Remediation is available by upgrading affected packages to version 4.4.7, 3.21.7.
pkg:npm/nuxt
Vulnerability advisories affecting package pkg:npm/nuxt. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-534h-c3cw-v3h9 | CVE-2026-56301 | MODERATE | Nuxt dev server vite-node IPC socket is world-connectable on Linux |
| GHSA-2x6f-57hp-86fx | - | MODERATE | Duplicate Advisory: Nuxt dev server vite-node IPC socket is world-connectable on Linux |
| GHSA-c9cv-mq2m-ppp3 | CVE-2026-56326 | MODERATE | Nuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via the `open` option, and protocol-relative bypass in `reloadNuxtApp` |
| GHSA-m3q2-p4fw-w38m | CVE-2026-56317 | LOW | Cross-site scripting via <NoScript> slot content in Nuxt's head components |
| GHSA-xppm-jmw6-fhmf | - | LOW | Duplicate Advisory: Cross-site scripting via <NoScript> slot content in Nuxt's head components |
| GHSA-934w-87qh-qr26 | CVE-2026-53722 | MODERATE | Nuxt: Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URL |
| GHSA-7c4v-fwgw-9rf7 | CVE-2026-72744 | MODERATE | Nuxt dev server discloses project root and workspace UUID via the Chrome DevTools workspace endpoint |
| GHSA-4jjw-pwvw-q6w3 | - | MODERATE | Duplicate Advisory: Nuxt dev server discloses project root and workspace UUID via the Chrome DevTools workspace endpoint |
| GHSA-9pgf-384g-p7mv | CVE-2026-71321 | HIGH | Nuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validation |
| GHSA-9473-5f9j-94wq | CVE-2026-71320 | HIGH | Nuxt: Server-Side Remote Code Execution via Runtime Template Injection in Nuxt Server Island Props |
| GHSA-48hr-524c-v5w3 | CVE-2026-71318 | MODERATE | Nuxt: Unauthorized Component Instantiation via Server Island Props |
| GHSA-wm8w-6qjm-cv43 | CVE-2026-71316 | HIGH | Nuxt runtime payload cache discloses another user's SSR data across users and to unauthenticated clients |
| GHSA-hxvh-4h3w-prp9 | CVE-2026-71315 | HIGH | Nuxt route rules silently dropped for mixed-case paths, bypassing appMiddleware auth gates (incomplete fix for CVE-2026-53721) |
| GHSA-hxcr-hm88-mpq6 | CVE-2026-71314 | HIGH | Nuxt: Unauthenticated out-of-memory crash via unbounded v-for expansion in island rendering |
| GHSA-hg3f-28rg-4jxj | CVE-2026-47200 | MODERATE | Nuxt's route middleware is not enforced when rendering `.server.vue` pages via `/__nuxt_island/page_*` |
| GHSA-g8wj-3cr3-6w7v | CVE-2026-46342 | LOW | Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoning |
| GHSA-fx6j-w5w5-h468 | CVE-2026-45669 | MODERATE | Nuxt: Reflected XSS in `navigateTo()` external redirect |
| GHSA-mm7m-92g8-7m47 | CVE-2026-53721 | HIGH | Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher |
| GHSA-rq7w-g337-39qq | - | LOW | Nuxt: Dev server discloses project absolute path and persistent workspace UUID via `/.well-known/appspecific/com.chrome.devtools.json` |
| GHSA-p6jq-8vc4-79f6 | CVE-2025-59414 | LOW | Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revival |
| GHSA-vf6r-87q4-2vjf | CVE-2024-34343 | MODERATE | nuxt vulnerable to Cross-site Scripting in navigateTo if used after SSR |
| GHSA-jvhm-gjrh-3h93 | CVE-2025-27415 | HIGH | Nuxt allows DOS via cache poisoning with payload rendering response |
| GHSA-v784-fjjh-f8r4 | CVE-2024-34344 | CRITICAL | Nuxt vulnerable to remote code execution via the browser when running the test locally |
| GHSA-gc34-5v43-h7v8 | CVE-2023-3224 | CRITICAL | nuxt Code Injection vulnerability |
CVE-2026-56301 at a Glance
Security Impact
CVSS: 5.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2026-56301
To remediate this vulnerability, upgrade all affected Nuxt dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install nuxt@4.4.7
npm install nuxt@3.21.7
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls nuxt
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-56301, inspect your project dependencies using npm:
npm ls nuxt
Analyze the terminal output to locate any version of Nuxt in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.4.7), your application is affected.
Note: The npm ls nuxt command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-276: Incorrect Default Permissions, where during installation, installed file permissions are set to allow anyone to modify those files. In Nuxt, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-56301 Affected Nuxt Versions
2 component(s)References
Frequently Asked Questions
What is CVE-2026-56301?
Which Nuxt versions are affected?
What version fixes CVE-2026-56301?
Is nuxt affected?
What is the CVSS score of CVE-2026-56301?
What CWE is associated with CVE-2026-56301?
How can I check npm dependencies for CVE-2026-56301?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-534h-c3cw-v3h9",
"modified" : "2026-09-23T21:25:56Z",
"published" : "2026-06-16T13:49:10Z",
"aliases" : [ "CVE-2026-56301" ],
"summary" : "Nuxt dev server vite-node IPC socket is world-connectable on Linux",
"details" : "### Impact\n\nWhen running `nuxt dev` on Linux (Node.js 20+, outside Docker / StackBlitz), Nuxt's internal vite-node IPC server binds to a Linux abstract-namespace Unix socket (`\\0nuxt-vite-node-<pid>-<ts>.sock`). Abstract sockets have no filesystem inode and therefore no permission bits: any local UID on the host that can read `/proc/net/unix` can enumerate the socket and connect to it.\n\nThe IPC server does not perform any peer-credential or shared-secret check before dispatching requests. The `module` request type passes its `moduleId` field straight into Vite's SSR `fetchModule()`, which is not gated by Vite's HTTP-layer `server.fs.allow` deny-list. A co-resident unprivileged local user can therefore request paths like `/home/<dev>/project/.env?raw` or `~/.ssh/id_rsa?raw` and read the developer's secrets through the dev server's SSR plugin pipeline. The `resolve` request type additionally enables filesystem probing.\n\nThis affects developers running `nuxt dev` on shared multi-tenant Linux hosts (lab machines, shared bastions, CI runners shared between jobs without per-job container isolation). It does not affect:\n\n- Production builds (`nuxt build` / `nuxt start`). The IPC server only runs in development.\n- macOS or Windows developers.\n- Docker / StackBlitz environments, which already fall back to a filesystem socket.\n- Single-user laptops or per-job containerised CI.\n\n### Patches\n\nFixed in `nuxt@4.4.7` (commit [`1f9f4767`](https://github.com/nuxt/nuxt/commit/1f9f4767a8725104da9bee872bb8d35246f25ae5)) and backported to `nuxt@3.21.7` (commit [`c293bf95`](https://github.com/nuxt/nuxt/commit/c293bf9503ccb3bc9559bff4a1f592f99063c9ea)).\n\nThe fix removes the abstract-namespace branch entirely. The IPC server now always binds to a filesystem Unix socket under the OS temp directory and explicitly `chmod 0600`s it after `listen()`, restricting connections to the owning UID. If the chmod fails for any reason, the server closes rather than serve requests on an unrestricted channel.\n\n### Workarounds\n\nIf you cannot upgrade immediately on an affected host:\n\n- Run `nuxt dev` inside a container or VM with no other tenants. Docker already triggers the filesystem-socket fallback in vulnerable versions and that fallback is unaffected.\n- Bind the dev process to a single-user namespace (`unshare -U`, rootless containers).\n- Restrict `/proc/net/unix` visibility via `hidepid=2` mount options where applicable, though this is partial mitigation only.\n\n### References\n\n- Affected file: `packages/vite/src/plugins/vite-node.ts`\n- CWE-276: Incorrect Default Permissions\n\n### Credit\n\nReported by Anthropic / Claude as part of Anthropic's coordinated vulnerability disclosure programme, reference ANT-2026-MSNKZFAT. Thanks to the Anthropic security team for the report and the detailed reproduction.\n\nIndependently reported by [@alcls01111](https://github.com/alcls01111) via GitHub's coordinated disclosure flow (`GHSA-5gvc-46gq-948j`), closed as a duplicate of this advisory.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "nuxt"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "4.4.7"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "nuxt"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.18.0"
}, {
"fixed" : "3.21.7"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/nuxt/nuxt/security/advisories/GHSA-534h-c3cw-v3h9"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-56301"
}, {
"type" : "WEB",
"url" : "https://github.com/nuxt/nuxt/commit/1f9f4767a8725104da9bee872bb8d35246f25ae5"
}, {
"type" : "WEB",
"url" : "https://github.com/nuxt/nuxt/commit/c293bf9503ccb3bc9559bff4a1f592f99063c9ea"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/nuxt/nuxt"
}, {
"type" : "WEB",
"url" : "https://www.vulncheck.com/advisories/nuxt-arbitrary-file-read-via-world-connectable-vite-node-ipc-socket-on-linux"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-276" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-16T13:49:10Z",
"nvd_published_at" : null
}
}