Servers and applications
GHSA-534h-c3cw-v3h9
Nuxt dev server vite-node IPC socket is world-connectable on Linux
- Severity
- Medium 5.5
- Published
- 2 Jun 2026
- Last changed
- 2 Jun 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.21.7, 4.4.7
- Attack
- Needs local access · Needs a user account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Sources
- Project advisories (GitHub)
Description
When 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--.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.
The 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//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.
Workarounds
If you cannot upgrade immediately on an affected host:
- 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.
- Bind the dev process to a single-user namespace (unshare -U, rootless containers).
- Restrict /proc/net/unix visibility via hidepid=2 mount options where applicable, though this is partial mitigation only.
Affected software
| Software | Affected versions |
|---|---|
NuxtServers and applications · github:nuxt/nuxt |
|
About Nuxt
JavaScript framework
- Developers who used it in the past year
- 4%Stack Overflow Developer Survey 2025, 2025
- Weekly downloads (npm)
- 3,404,733npm, 15 Nov 2026
- GitHub stars
- 61,078GitHub, 15 Nov 2026
- Forks
- 5,837GitHub, 15 Nov 2026
- Latest release
- v4.6.4GitHub, 15 Nov 2026
- Released
- 2 Nov 2026GitHub
- License
- MIT LicenseWikidata
- Written in
- JavaScript, Vue.jsWikidata
- First published on GitHub
- 26 Oct 2016GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4 | 4.6.4 | Yes |
| 3 | 3.21.11 | Ended 31 Jul 2026 |
| 2 | 2.18.1 | Ended 30 Jun 2024 |
| 1 | 1.4.5 | Ended 21 Sept 2019 |
From endoflife.date.
Vulnerabilities in Nuxt
- In our list
- 49
- Published in the last 12 months
- 46
- Critical, last 12 months
- 1
- High, last 12 months
- 8
- Known exploited
- 0
- CVE-2023-54417Nuxt 3.0.0 < 3.4.2 Unauthenticated File Read via vite-node Dev ServerHigh 8.7 18 Nov 2026
- CVE-2023-54418Nuxt 3.0.0-rc.1 < 3.0.0-rc.13 Unauthenticated Arbitrary File Read via Vite Dev ServerHigh 8.7 18 Nov 2026
- GHSA-r99w-jh2x-3mg9Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routesMedium 6.5 2 Nov 2026
- CVE-2026-128077Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routesMedium 6.5 2 Nov 2026
- GHSA-hf59-9xwc-2g4pColliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)Low 3.1 2 Nov 2026
- CVE-2026-128076Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)Low 3.1 2 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-534h-c3cw-v3h9
- github.com https://github.com/nuxt/nuxt/security/advisories/GHSA-534h-c3cw-v3h9