CVE-2026-71319
Nuxt.js Unauthenticated WebSocket RPC Call Leading to Remote Code Execution
Description
Nuxt is an open-source web development framework for Vue.js. Prior to 3.3.1, 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://<host>:<port>/, 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: '<command>' }) then openInEditor('<any-existing-file>') to execute an arbitrary program on the developer's machine. This issue is fixed in 3.3.1.
INFO
Published Date :
Aug. 5, 2026, 10:17 p.m.
Last Modified :
Oct. 24, 2026, 3:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | CRITICAL | [email protected] | ||||
| CVSS 3.1 | CRITICAL | MITRE-CVE |
Solution
- Update Nuxt to version 3.3.1 or later.
- Ensure HMR WebSocket is not exposed externally.
- Review RPC channel authentication mechanisms.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-71319.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-71319 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-71319
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-71319 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-71319 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 24, 2026
Action Type Old Value New Value Changed Translation Title: devtools de nuxt, Description: Nuxt es un framework de desarrollo web de código abierto para Vue.js. Antes de la versión 3.3.1, Nuxt DevTools (solo en modo de desarrollo) expone un canal RPC bidireccional a través del WebSocket HMR de Vite mediante el plugin nuxt:devtools:rpc. En las versiones afectadas, el canal no tiene autenticación: cualquier cliente que pueda alcanzar el endpoint HMR de Vite (ws://[host]:[port]/, subprotocolo vite-hmr) puede llamar a métodos RPC, sin token, handshake o verificación de origen antes de que se establezca el canal. Los métodos updateOptions(), clearOptions() y openInEditor() no aplican la verificación ensureDevAuthToken que utilizan los otros métodos mutadores. openInEditor() lee el valor persistido behavior.openInEditor y lo pasa al paquete launch-editor, que lo genera como un proceso hijo. Ese valor es configurable a través del igualmente no autenticado updateOptions(). Un atacante que pueda alcanzar el puerto HMR puede, por lo tanto, encadenar updateOptions(’behavior’, { openInEditor: ’[command]’ }) y luego openInEditor(’[any-existing-file]’) para ejecutar un programa arbitrario en la máquina del desarrollador. Este problema está solucionado en la versión 3.3.1. Title: devtools de nuxt, Description: Nuxt es un framework de desarrollo web de código abierto para Vue.js. Antes de la versión 3.3.1, Nuxt DevTools (solo en modo de desarrollo) expone un canal RPC bidireccional a través del WebSocket HMR de Vite mediante el plugin nuxt:devtools:rpc. En las versiones afectadas, el canal no tiene autenticación: cualquier cliente que pueda alcanzar el endpoint HMR de Vite (ws://[host]:[port]/, subprotocolo vite-hmr) puede llamar a métodos RPC, sin token, handshake o verificación de origen antes de que se establezca el canal. Los métodos updateOptions(), clearOptions() y openInEditor() no aplican la verificación ensureDevAuthToken que utilizan los otros métodos mutadores. openInEditor() lee el valor persistido behavior.openInEditor y lo pasa al paquete launch-editor, que lo genera como un proceso hijo. Ese valor es configurable a través del igualmente no autenticado updateOptions(). Un atacante que pueda alcanzar el puerto HMR puede, por lo tanto, encadenar updateOptions(’behavior’, { openInEditor: ’[command]’ }) y luego openInEditor(’[any-existing-file]’) para ejecutar un programa arbitrario en la máquina del desarrollador. Este problema está solucionado en la versión 3.3.1. -
CVE Translated by [email protected]
Oct. 23, 2026
Action Type Old Value New Value Added Translation Title: devtools de nuxt, Description: Nuxt es un framework de desarrollo web de código abierto para Vue.js. Antes de la versión 3.3.1, Nuxt DevTools (solo en modo de desarrollo) expone un canal RPC bidireccional a través del WebSocket HMR de Vite mediante el plugin nuxt:devtools:rpc. En las versiones afectadas, el canal no tiene autenticación: cualquier cliente que pueda alcanzar el endpoint HMR de Vite (ws://[host]:[port]/, subprotocolo vite-hmr) puede llamar a métodos RPC, sin token, handshake o verificación de origen antes de que se establezca el canal. Los métodos updateOptions(), clearOptions() y openInEditor() no aplican la verificación ensureDevAuthToken que utilizan los otros métodos mutadores. openInEditor() lee el valor persistido behavior.openInEditor y lo pasa al paquete launch-editor, que lo genera como un proceso hijo. Ese valor es configurable a través del igualmente no autenticado updateOptions(). Un atacante que pueda alcanzar el puerto HMR puede, por lo tanto, encadenar updateOptions(’behavior’, { openInEditor: ’[command]’ }) y luego openInEditor(’[any-existing-file]’) para ejecutar un programa arbitrario en la máquina del desarrollador. Este problema está solucionado en la versión 3.3.1. -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Aug. 07, 2026
Action Type Old Value New Value Changed SSVC {'id': 'CVE-2026-71319', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-08-06T14:38:40.363333Z'} {'id': 'CVE-2026-71319', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-08-06T00:00:00+00:00'} -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Aug. 06, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-71319', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-08-06T14:38:40.363333Z'} -
New CVE Received by [email protected]
Aug. 05, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'nuxt', 'product': 'devtools', 'versions': [{'status': 'affected', 'version': '< 3.3.1'}]}] Added Description Nuxt is an open-source web development framework for Vue.js. Prior to 3.3.1, 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://<host>:<port>/, 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: '<command>' }) then openInEditor('<any-existing-file>') to execute an arbitrary program on the developer's machine. This issue is fixed in 3.3.1. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Added CWE CWE-94 Added CWE CWE-306 Added Reference https://github.com/nuxt/devtools/commit/a7b2718b930766e1ffb0640259d53f5b041a50b4 Added Reference https://github.com/nuxt/devtools/releases/tag/v3.3.1 Added Reference https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv