CVE-2026-71319: @nuxt/devtools Unauthenticated Nuxt DevTools RPC Allows Vulnerability

CRITICAL
Advisory Identifier: GHSA-279x-mwfv-vcqv
Share
CVSS 9.6
CWE-94 CWE-306
Published
Advisory Summary

CVE-2026-71319 is a CRITICAL (CVSS 9.6) unauthenticated nuxt devtools rpc allows vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting @nuxt/devtools libraries in the npm ecosystem. The issue involves unauthenticated nuxt devtools rpc allows arbitrary command execution on the developer's host. Remediation is available by upgrading affected packages to version 3.3.1.

CVE-2026-71319 at a Glance

CVE Identifier CVE-2026-71319
GHSA Identifier GHSA-279x-mwfv-vcqv
Severity CRITICAL
CVSS v3.1 Base Score 9.6
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product @nuxt/devtools
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-71319

To remediate this vulnerability, upgrade all affected @nuxt/devtools dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@nuxt/devtools fixed: 3.3.1 
npm install @nuxt/devtools@3.3.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @nuxt/devtools

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-71319, inspect your project dependencies using npm:

npm ls @nuxt/devtools

Analyze the terminal output to locate any version of @nuxt/devtools in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.3.1), your application is affected.

Note: The npm ls @nuxt/devtools 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-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In @nuxt/devtools, 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

### Impact 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. The HMR port is reachable by a process on the same host, by any peer on the LAN when the dev server is bound with `nuxi dev --host`, or by a malicious website the developer visits while the dev server is running (a browser can open the HMR WebSocket cross-origin). Impact is limited to development environments; production builds do not run DevTools. ### Patches Fixed in `@nuxt/devtools@3.3.1`. Because `nuxt` depends on `@nuxt/devtools` through a `^3.x` range, updating is a lockfile refresh / reinstall; no `nuxt` release is required. ### 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`. ### References - GHSA-279x-mwfv-vcqv - `launch-editor`: https://www.npmjs.com/package/launch-editor

CVE-2026-71319 Affected @nuxt/devtools Versions

1 component(s)
Fixed Versions:
3.3.1
Product / Package Ecosystem Affected Versions Fixed Version
@nuxt/devtools
npm/@nuxt/devtools
npm
< 3.3.1
3.3.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv
@nuxt/devtools Source Repository REPOSITORY
https://github.com/nuxt/nuxt

Frequently Asked Questions

What is CVE-2026-71319?
CVE-2026-71319 is a security vulnerability in @nuxt/devtools involving Unauthenticated Nuxt DevTools RPC allows arbitrary command execution on the developer's host under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which @nuxt/devtools versions are affected?
Affected versions include releases prior to 3.3.1 across affected packages: @nuxt/devtools.
What version fixes CVE-2026-71319?
Upgrading to 3.3.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @nuxt/devtools affected?
Yes, @nuxt/devtools is affected in releases prior to 3.3.1. Upgrade your dependency to 3.3.1 or later.
What is the CVSS score of CVE-2026-71319?
CVE-2026-71319 has a CVSS v3.1 base score of 9.6 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-71319?
CVE-2026-71319 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check npm dependencies for CVE-2026-71319?
Run the dependency tree command: 'npm ls @nuxt/devtools'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-279x-mwfv-vcqv",
  "modified" : "2026-08-05T21:27:39Z",
  "published" : "2026-08-05T21:27:39Z",
  "aliases" : [ "CVE-2026-71319" ],
  "summary" : "Unauthenticated Nuxt DevTools RPC allows arbitrary command execution on the developer's host",
  "details" : "### Impact\n\nNuxt 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.\n\n`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.\n\nThe HMR port is reachable by a process on the same host, by any peer on the LAN when the dev server is bound with `nuxi dev --host`, or by a malicious website the developer visits while the dev server is running (a browser can open the HMR WebSocket cross-origin). Impact is limited to development environments; production builds do not run DevTools.\n\n### Patches\n\nFixed in `@nuxt/devtools@3.3.1`. Because `nuxt` depends on `@nuxt/devtools` through a `^3.x` range, updating is a lockfile refresh / reinstall; no `nuxt` release is required.\n\n### Workarounds\n\n- Update `@nuxt/devtools` to a patched version.\n- Do not run the dev server bound to a non-loopback interface (`nuxi dev --host`) on an untrusted network.\n- Disable DevTools entirely with `devtools: { enabled: false }` in `nuxt.config`.\n\n### References\n\n- GHSA-279x-mwfv-vcqv\n- `launch-editor`: https://www.npmjs.com/package/launch-editor",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nuxt/devtools"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.3.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nuxt/nuxt"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-306", "CWE-94" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-05T21:27:39Z",
    "nvd_published_at" : null
  }
}