Skip to content

chore(deps): update devdependency @nuxt/devtools to v3 [security] - #2066

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-nuxt-devtools-vulnerability
Open

chore(deps): update devdependency @nuxt/devtools to v3 [security]#2066
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-nuxt-devtools-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@nuxt/devtools (source) ^2.1.3^3.0.0 age confidence

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

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

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

v3.2.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.3

Compare Source

Bug Fixes

v3.2.2

Compare Source

Bug Fixes
Features

v3.2.1

Compare Source

Bug Fixes

v3.2.0

Compare Source

Bug Fixes
  • devtools: call devtools:initialized hook after all modules run (#​919) (3662836)
Features
  • enhance inspect panel, add copy visual info for agents (#​928) (6bb2565)
  • upgrade vite-devtools (5c4a0b0)

3.1.1 (2025-11-25)

Bug Fixes
Features
  • support passing additional permissions to the iframe (#​911) (bc1d11c)

v3.1.1

Compare Source

Bug Fixes
Features
  • support passing additional permissions to the iframe (#​911) (bc1d11c)

v3.1.0

Compare Source

Features

3.0.1 (2025-10-31)

Bug Fixes
  • update text color for default inputs description (#​904) (8cd29b7)
Features
  • add expiermental support for Vite DevTools (681378a)
  • improve vite devtools integration (8759cf3)

v3.0.1

Compare Source

Bug Fixes
  • update text color for default inputs description (#​904) (8cd29b7)
Features
  • add expiermental support for Vite DevTools (681378a)
  • improve vite devtools integration (8759cf3)

v3.0.0

Compare Source

v2.7.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.6.5

Compare Source

Bug Fixes
  • ensure path resolve is safe (1fabb49)

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.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.26%. Comparing base (3bbe949) to head (be74a12).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2066   +/-   ##
=======================================
  Coverage   99.26%   99.26%           
=======================================
  Files          83       83           
  Lines        3244     3244           
  Branches      562      562           
=======================================
  Hits         3220     3220           
  Misses         17       17           
  Partials        7        7           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant