Servers and applications
CVE-2026-71319
Unauthenticated Nuxt DevTools RPC allows arbitrary command execution on the developer's host
- Severity
- Critical 9.6
- Published
- 27 Jul 2026
- Last changed
- 5 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.3.1
- Exploit chance
- 0.6% in the next 30 daysHigher than 50% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · Needs someone to click or open something
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H- Also known as
- GHSA-279x-mwfv-vcqv
- Sources
- Project advisories (GitHub)
Description
Nuxt DevTools (development mode only) exposes a bidirectional RPC channel over the Vite HMR WebSocket via the nuxt:devtools:rpc plugin. On affected versions the channel has no authentication: any client that can reach the Vite HMR endpoint (ws://:/, subprotocol vite-hmr) can call RPC methods, with no token, handshake, or origin check before the channel is established. The updateOptions(), clearOptions(), and openInEditor() methods do not enforce the ensureDevAuthToken check that the other mutating methods use.
openInEditor() reads the persisted behavior.openInEditor value and passes it to the launch-editor package, which spawns it as a child process. That value is settable through the equally unauthenticated updateOptions(). An attacker who can reach the HMR port can therefore chain updateOptions('behavior', { openInEditor: '' }) then openInEditor('') to execute an arbitrary program on the developer's machine.
Workarounds
- Update @nuxt/devtools to a patched version.
- Do not run the dev server bound to a non-loopback interface (nuxi dev --host) on an untrusted network.
- Disable DevTools entirely with devtools: { enabled: false } in nuxt.config.
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
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-71319
- GitHub Advisory Database https://github.com/advisories/GHSA-279x-mwfv-vcqv
- github.com https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv