chore(deps): update devdependency @nuxt/devtools to v3.3.1 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@nuxt/devtools (source)	3.2.4 → 3.3.1

---

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

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

More information

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

Severity

• CVSS Score: 9.6 / 10 (Critical)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

References

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

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nuxt/devtools (@​nuxt/devtools)

v3.3.1

Compare Source

No significant changes

    View changes on GitHub

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​nuxt/​devtools-kit@​3.3.1
	@​nuxt/​devtools@​3.3.1

View full report

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/hints@381

commit: f89c0e1