Nuxt dev server arbitrary file read through client error reports
Impact
Nuxt dev server versions 4.6.0 to 4.6.2 are vulnerable to arbitrary file read through client error reports. An attacker with TCP access to the dev server can read files readable by the dev process. This requires exposing the dev server to a network.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.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.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 4.6.0 before 4.6.3Semantic versions | 4.6.3 |
Version evidence: OSV · GHSA-x287-wcfc-q46c
View original version evidence (0 explicit versions)
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
nuxt · GitHub_M
nuxt
1 range
nuxt · GitHub_M
nuxt
Compare with this publisher’s ranges. This does not inspect your installation.
affected
>= 4.6.0, < 4.6.3
Other versions: unknown
Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-119198View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.