CVE-2026-119198: Nuxt dev server arbitrary file read through client error reports
The Nuxt dev server in versions 4.6.0 to 4.6.2 (`@nuxt/vite-builder`) can be made to read any file the dev process can read. A client sends a `nuxt:dev:client-error` event ending in an absolute path, and the file content comes back in the error report. It matters when the dev server is reachable from a network. Upgrade to 4.6.3.
Published Oct 30, 2026 · Analysis Oct 31, 2026
What an attacker can do
A client connected to the dev server's HMR socket can send a nuxt:dev:client-error event whose message ends in an absolute file path. While building the error report, the dev server reads that file. The contents come back in the error overlay, on the dev error channel and in the terminal report. Vite's server.fs allow list blocks the same path over /_nuxt/@fs/, but the client error channel bypasses that check.
Only the dev server is affected. Production builds contain none of this code, and Nuxt 3 is not affected.
The attacker needs TCP access to the dev port. With the default localhost bind, that means a local process, which can usually read the same files anyway. The risk is real when the server is exposed with nuxt dev --host, nuxt dev --tunnel or a proxy onto the dev port. Then anyone who can reach the port can read SSH keys, .env files, cloud credentials and other files outside the project. No user interaction is needed, and a plain WebSocket client works if it does not send Sec-Fetch-Site: cross-site. A web page on another origin cannot fetch the report, because the overlay and channel endpoints reject other-origin browser requests.
Who is affected
@nuxt/vite-builder 4.6.0 up to but not including 4.6.3, which means nuxt 4.6.0 to 4.6.2. Nuxt 3 is not affected. Exposure needs the dev server running on a reachable interface. Check versions:
npm ls nuxt @nuxt/vite-builderAlso review how you start the dev server: nuxt dev --host, nuxt dev --tunnel, dev containers with published ports, or reverse proxies in front of the dev port.
@nuxt/vite-builder
- Ecosystem
- npm
- Affected
- >= 4.6.0, < 4.6.3
- Fixed in
- 4.6.3
- Check
npm ls @nuxt/vite-builder
How to fix it
Upgrade to nuxt 4.6.3, which depends on @nuxt/vite-builder 4.6.3:
npm install [email protected]The patch stops turning a client-reported error into a compile report. Report building for it no longer reads the filesystem, and file content comes only from the dev server's module graph.
Workaround: keep the default localhost bind and avoid --host, --tunnel and proxies onto the dev port. If the dev port was reachable from an untrusted network while a vulnerable version ran, treat every file the dev process could read as exposed. Rotate SSH keys and .env secrets.
How to tell if you were hit
Check which dev servers ran 4.6.0 to 4.6.2 on a reachable interface, such as tunnels, shared networks or cloud dev boxes. Look in proxy or tunnel logs for WebSocket connections to the HMR socket from unknown addresses. Look in the dev terminal for error reports that print contents of files outside the project, such as keys or .env files. A report built from a nuxt:dev:client-error event that names an absolute path is the sign of this attack. If you find any, rotate the credentials that the dev user could read.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
A client that can connect to the dev server's HMR socket can send a nuxt:dev:client-error event whose message ends in an absolute file path. The dev server reads that file while building the error report, and its contents are returned in the error overlay, on the dev error channel, and in the report shown in the terminal.
Impact
This affects the development server only; production builds contain none of this code. Affected versions are 4.6.0 to 4.6.2.
Reading the file requires TCP access to the dev server, so the default localhost bind limits this to local processes, which can usually read the same files directly. With the dev server exposed to a network (nuxt dev --host, nuxt dev --tunnel, or a proxy onto the dev port), anyone who can reach the port can read any file the dev process can read: SSH keys, .env files, cloud credentials and other files outside the project. The same path is refused by Vite's server.fs allow list over /_nuxt/@fs/; the client error channel bypasses that check.
No user interaction is needed and no browser is involved: a plain WebSocket client is enough, as long as it does not send Sec-Fetch-Site: cross-site. A web page on another origin cannot retrieve the report: the overlay and channel endpoints reject browser requests from other origins.
Nuxt 3 is not affected.
Patches
Fixed in @nuxt/vite-builder 4.6.3, which nuxt 4.6.3 depends on. A client-reported error is no longer turned into a compile report, and report building for it no longer reads from the filesystem; file content now comes only from the dev server's module graph.
Workarounds
Do not expose the dev server to untrusted networks: keep the default localhost bind, and avoid nuxt dev --host, nuxt dev --tunnel and proxies onto the dev port. If the dev port was reachable from an untrusted network while a vulnerable version was running, treat any file readable by the dev process on that machine as exposed, and rotate credentials such as SSH keys and .env secrets.
Credits
Thanks to @samsulselfut for the report.
Credited to samsulselfut.
Questions
- Does CVE-2026-119198 affect production Nuxt apps?
No. The advisory says production builds contain none of the vulnerable code. Only the development server in Nuxt 4.6.0 to 4.6.2 is affected.
- Can a malicious website exploit this against my localhost dev server?
The advisory says no. The overlay and channel endpoints reject browser requests from other origins, so a page on another origin cannot retrieve the report. A plain WebSocket client with network access is needed.
- Is Nuxt 3 affected?
No. The advisory states Nuxt 3 is not affected. The affected range is 4.6.0 to 4.6.2, fixed in 4.6.3.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-119199
Nuxt dev server exposes private runtime config through the Nitro dev bundle
medium5.9Oct 30, 2026CVE-2026-119201
Nuxt dev server exposes generated appSecret through Vite file serving
medium4.8Oct 30, 2026CVE-2025-24360
Opening a malicious website while running a Nuxt dev server could allow read-only access to code
medium5.3Jan 27, 2025
