# CVE-2026-71319: Nuxt.js Unauthenticated WebSocket RPC Call Leading to Remote Code Execution

> Unauthenticated WebSocket RPC in Nuxt DevTools allows attackers to execute arbitrary code on developer machines via command injection.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-279x-mwfv-vcqv

## What is CVE-2026-71319?

CVE-2026-71319 is a critical code injection vulnerability in nuxt devtools, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Nuxt is an open-source web development framework for Vue.js. Prior to 3.3.1, 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. This issue is fixed in 3.3.1.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-71319?

2 open source packages ship an affected version, including @nuxt/devtools.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nuxt/devtools` | npm | All versions | 3.3.1 |
| `@nuxt/devtools` | npm | All versions | 3.3.1 |

## How do I fix CVE-2026-71319?

Upgrade @nuxt/devtools to 3.3.1 or later.

## Is CVE-2026-71319 being exploited?

There is no known exploitation of CVE-2026-71319 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71319 and fix it if it is affected.

What it is: CVE-2026-71319 is a critical code injection vulnerability in nuxt devtools, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-71319 in the wild and no public exploit code.

Affected packages and fixed versions:
- @nuxt/devtools (npm): affected all versions; fixed in 3.3.1
- @nuxt/devtools (npm): affected all versions; fixed in 3.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71319/ (Markdown: https://insights.sbomify.com/CVE-2026-71319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71319
- OSV: https://osv.dev/vulnerability/CVE-2026-71319

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71319/
Summaries are generated and may contain mistakes; the official description above is the record.