ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-119198

Nuxt dev server arbitrary file read through client error reports

Published Oct 27, 2026 · catalog updated Oct 30, 2026 · Nuxt dev server arbitrary

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-119198. EPSS is 0.29%. Act only if a listed version of Nuxt dev server arbitrary is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Nuxt dev server arbitrary).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.29%
Remediation
Version ranges on file
Affected products
npm @nuxt · npm @nuxt/vite-builder

### Summary A client that can connect to the dev server's HMR socket can send a 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 to . 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 ( , , or a proxy onto the dev port), anyone who can reach the port can read any file the dev process can read: SSH keys, files, cloud credentials and other files outside the project. The same path is refused by Vite's allow list over ; 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 . 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 4.6.3, which 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 , 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 secrets. ### Credits Thanks to [@samsulselfut](https://github.com/samsulselfut) for the report.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @nuxtversion unspecified
  • npm @nuxt/vite-builder>= 4.6.0 < 4.6.3
  • npm @nuxt/vite-builder>= 4.6.0, < 4.6.3

How to fix CVE-2026-119198

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-119198. EPSS is 0.29%. Act only if a listed version of Nuxt dev server arbitrary is installed.

Which versions are affected?

Compare what you have installed with >= 4.6.0 < 4.6.3, >= 4.6.0, < 4.6.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-73. EPSS 0.29%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Nuxt security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 30, 2026 · GitHub Advisory Database

    Detected

    ### Summary A client that can connect to the dev server's HMR socket can send a 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

  2. Oct 30, 2026 · GitHub Advisory Database

    Updated

    ### Summary A client that can connect to the dev server's HMR socket can send a 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

Sources

  • CVE.orgVulnerability recordCVE-2026-119198

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-x287-wcfc-q46c

    Nuxt dev server arbitrary file read through client error reports

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-119198

    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.

    advisories.gitlab.com
  • Maintainer security tabsVendor advisoryGHSA-x287-wcfc-q46c

    ### Summary A client that can connect to the dev server's HMR socket can send a 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

    github.com

References

Freshness

Last verified in this catalog Oct 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026
  • GitLab Advisory DatabaseNov 1, 2026
  • CVE.orgOct 31, 2026
  • GitHub Advisory DatabaseOct 31, 2026