ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-71319

Unauthenticated Nuxt DevTools RPC allows arbitrary command execution on the developer's host

Published Jul 27, 2026 · catalog updated Aug 5, 2026 · Unauthenticated Nuxt DevTools RPC

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-71319. EPSS is 0.63%. Act only if a listed version of Unauthenticated Nuxt DevTools RPC is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Unauthenticated Nuxt DevTools RPC).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.63%
Remediation
Version ranges on file
Affected products
npm @nuxt/devtools

### Impact Nuxt DevTools (development mode only) exposes a bidirectional RPC channel over the Vite HMR WebSocket via the plugin. On affected versions the channel has no authentication: any client that can reach the Vite HMR endpoint ( , subprotocol ) can call RPC methods, with no token, handshake, or origin check before the channel is established. The , , and methods do not enforce the check that the other mutating methods use. reads the persisted value and passes it to the package, which spawns it as a child process. That value is settable through the equally unauthenticated . An attacker who can reach the HMR port can therefore chain then 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 , 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 . Because depends on through a range, updating is a lockfile refresh / reinstall; no release is required. ### Workarounds - Update to a patched version. - Do not run the dev server bound to a non-loopback interface ( ) on an untrusted network. - Disable DevTools entirely with in . ### References - GHSA-279x-mwfv-vcqv - : https://www.npmjs.com/package/launch-editor

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @nuxt/devtools< 3.3.1

How to fix CVE-2026-71319

  • Upgrade

    CVE-2026-71319 lists a fix boundary at 3.3.1. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 3.3.1

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-71319. EPSS is 0.63%. Act only if a listed version of Unauthenticated Nuxt DevTools RPC is installed.

Which versions are affected?

Compare what you have installed with < 3.3.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-306: Missing Authentication for Critical Function; CWE-94: Code Injection. EPSS 0.63%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Nuxt security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 27, 2026 · Maintainer security tabs

    Detected

    ### Impact Nuxt DevTools (development mode only) exposes a bidirectional RPC channel over the Vite HMR WebSocket via the plugin. On affected versions the channel has no authentication: any client that can reach the Vite HMR endpoint ( , subprotocol ) can call RPC methods, with no token, handshake, or origin check before the channel is established. The , , and methods do not enforce the check that

  2. Aug 5, 2026 · Maintainer security tabs

    Updated

    ### Impact Nuxt DevTools (development mode only) exposes a bidirectional RPC channel over the Vite HMR WebSocket via the plugin. On affected versions the channel has no authentication: any client that can reach the Vite HMR endpoint ( , subprotocol ) can call RPC methods, with no token, handshake, or origin check before the channel is established. The , , and methods do not enforce the check that

Sources

  • Maintainer security tabsVendor advisoryGHSA-279x-mwfv-vcqv

    ### Impact Nuxt DevTools (development mode only) exposes a bidirectional RPC channel over the Vite HMR WebSocket via the plugin. On affected versions the channel has no authentication: any client that can reach the Vite HMR endpoint ( , subprotocol ) can call RPC methods, with no token, handshake, or origin check before the channel is established. The , , and methods do not enforce the check that

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026