Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Nov 7, 2025 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

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

Nuxt DevTools vulnerable to cross-site scripting (XSS)

CVE-2025-52662 / GHSA-xmq3-q5pm-rp26

More information

Details

A vulnerability in Nuxt DevTools has been fixed in version 2.6.4*. This issue may have allowed Nuxt auth token extraction via XSS under certain configurations. All users are encouraged to upgrade.

Severity

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

References

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


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
    View changes on GitHub

v3.2.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.1.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.1.0

Compare Source

   🚀 Features
    View changes on GitHub

v3.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.0.0

Compare Source

   🚨 Breaking Changes
    View changes on GitHub

v2.7.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.6.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.6.4

Compare Source

   🐞 Bug Fixes
  • Using textContent instead of innerHtml for auth pagechore: update lock  -  by @​antfu (7cadb)
    View changes on GitHub

v2.6.3

Compare Source

No significant changes

    View changes on GitHub

v2.6.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.6.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.6.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    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.

@vercel

vercel Bot commented Nov 7, 2025 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
content Ignored Ignored Nov 16, 2026 5:52pm UTC

@coderabbitai

coderabbitai Bot commented Nov 7, 2025 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: b2f3dabc-4489-4fad-b876-58c897e52ea3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 1b3964f to 888b45c Compare November 10, 2025 17:34
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 888b45c to fede9ad Compare November 18, 2025 22:41
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from fede9ad to 9bbda56 Compare December 3, 2025 18:25
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 05119f3 to 8fe447d Compare December 31, 2025 20:09
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 8fe447d to 7095c2d Compare January 8, 2026 18:35
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 314626a to f4cd10b Compare January 23, 2026 18:15
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from f4cd10b to b69501c Compare February 2, 2026 17:38
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from e10ac51 to b0b3eec Compare February 17, 2026 15:07
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 08f6cf7 to 128031f Compare March 10, 2026 03:23
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 128031f to 782c989 Compare March 13, 2026 18:36
@renovate renovate Bot changed the title chore(deps): update dependency @nuxt/devtools to v2.6.4 [security] chore(deps): update dependency @nuxt/devtools to v2.6.4 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-nuxt-devtools-vulnerability branch March 27, 2026 01:18
@renovate renovate Bot changed the title chore(deps): update dependency @nuxt/devtools to v2.6.4 [security] - autoclosed chore(deps): update dependency @nuxt/devtools to v2.6.4 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 3 times, most recently from 9ef4055 to 4ffe03b Compare April 1, 2026 17:03
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 4ffe03b to 105f8af Compare April 8, 2026 21:08
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 105f8af to 9ae8e35 Compare April 29, 2026 13:45
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from ab59ee4 to a0d8cdc Compare May 18, 2026 10:00
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 78ca5bb to 292674e Compare June 1, 2026 18:48
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from d5d59c5 to 957b7f3 Compare July 16, 2026 16:00
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 4ab215d to ed2511f Compare July 24, 2026 19:55
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 29d2776 to 4a958cd Compare July 30, 2026 21:42
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from bd04d39 to 2cd0fc3 Compare August 14, 2026 21:08
@renovate renovate Bot changed the title chore(deps): update dependency @nuxt/devtools to v2.6.4 [security] chore(deps): update dependency @nuxt/devtools to v3 [security] Aug 26, 2026
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 2cd0fc3 to d028428 Compare August 26, 2026 14:14
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 5 times, most recently from 6190399 to 37bce29 Compare September 7, 2026 23:17
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 4 times, most recently from c1f5e18 to 8084c02 Compare September 16, 2026 06:33
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from ad292c2 to d999d29 Compare October 1, 2026 12:51
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from d999d29 to 3768a17 Compare October 5, 2026 18:54
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from ec6899e to 762072f Compare October 20, 2026 10:38
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 44af2f6 to e656dc8 Compare October 26, 2026 23:58
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 7a9d2a7 to bb8dabe Compare November 11, 2026 20:46
@renovate
renovate Bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from bb8dabe to 1dc13bf Compare November 16, 2026 17:52

This branch has not been deployed

No deployments
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.

0 participants