CVE-2026-71319: Nuxt DevTools command injection via unauthenticated RPC channel

CVE-2026-71319 · Severity: critical · CVSS 9.6 · Published 2026-08-05

Nuxt DevTools is a debugging interface for Vue.js web application development. An unauthenticated attacker who can reach the development server's HMR port can execute arbitrary commands on a developer's machine by chaining unprotected RPC method calls. This vulnerability only affects development environments, but could allow malware installation or data theft on a developer's workstation during active development.

Technologies: @nuxt/devtools (npm), Nuxt DevTools. Vendors: npm, Nuxt.

Quick answers

Is CVE-2026-71319 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-71319 being exploited in the wild.
How severe is CVE-2026-71319?
Critical severity, with a CVSS score of 9.6, published 5 August 2026.
Which products and versions are affected?
@nuxt/devtools (npm) < 3.3.1, SEMVER:introduced=0,fixed=3.3.1; Nuxt DevTools < 3.3.1.
Is there a fix for CVE-2026-71319?
Yes. @nuxt/devtools (npm): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-71319 attacked?
It is attacked over the network.
Am I affected by CVE-2026-71319?
Check whether you run @nuxt/devtools (npm) or Nuxt DevTools at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • @nuxt/devtools (npm): upgrade to 3.3.1 or later
    npm install @nuxt/devtools@3.3.1

Technical details

The vulnerability is a missing authentication control (CWE-306) combined with improper code generation (CWE-94) in Nuxt DevTools. The RPC channel over the Vite HMR WebSocket lacks authentication; any client reaching the ws://&lt;host&gt;:&lt;port&gt;/ endpoint with subprotocol vite-hmr can invoke RPC methods without tokens, handshakes, or origin checks. Specifically, updateOptions() and clearOptions() methods do not enforce the ensureDevAuthToken check used by other mutating methods. An attacker chains updateOptions('behavior', {openInEditor: '&lt;command&gt;'}) followed by openInEditor('&lt;any-existing-file&gt;') to execute an arbitrary program via the launch-editor package. Attack vectors include local processes on the same host, LAN peers when the dev server is bound with --host, and malicious websites visited by the developer (browsers can open HMR WebSocket cross-origin). The vulnerability is fixed in @nuxt/devtools version 3.3.1 and does not require a nuxt release since it only depends on the devtools package.

Affected products

  • Nuxt @nuxt/devtools < 3.3.1

Identifiers

  • CVE-2026-71319
  • GHSA-279x-mwfv-vcqv

Timeline

  • 2026-07-27: disclosed: Published on GitHub security advisory
  • 2026-08-05: patched: Fixed in @nuxt/devtools@3.3.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.