GHSA-279x-mwfv-vcqv

Source

https://github.com/advisories/GHSA-279x-mwfv-vcqv

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/08/GHSA-279x-mwfv-vcqv/GHSA-279x-mwfv-vcqv.json

JSON Data

https://api.test.osv.dev/v1/vulns/GHSA-279x-mwfv-vcqv

Aliases

CVE-2026-71319

Published

2026-08-05T21:27:39Z

Modified

2026-08-05T21:31:32.639961502Z

Severity

9.6 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H CVSS Calculator

Summary

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

Details

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

Database specific

{
    "github_reviewed": true,
    "nvd_published_at": null,
    "cwe_ids": [
        "CWE-94",
        "CWE-306"
    ],
    "severity": "CRITICAL",
    "github_reviewed_at": "2026-08-05T21:27:39Z"
}

References

Affected packages

npm / @nuxt/devtools

Package

Name: @nuxt/devtools; View open source insights on deps.dev
Purl: pkg:npm/%40nuxt/devtools

Affected ranges

Type: SEMVER
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

3.3.1

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/08/GHSA-279x-mwfv-vcqv/GHSA-279x-mwfv-vcqv.json"