Live › vulnerability › CVE-2026-119198
From Nuxt 4.6.0 through 4.6.2, a client that can reach the development server over TCP can send a crafted HMR client-error event containing an absolute file path. The dev server then returns that file's contents through its error overlay and terminal output, bypassing Vite's file allow list.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 21:26 UTC. All times on this page are UTC.
Only teams running the Nuxt 4 development server (nuxt dev) on versions 4.6.0 to 4.6.2 where the dev port is reachable from other machines. Production builds and Nuxt 3 are not affected, and the default localhost binding limits remote exposure. Teams that only build and deploy static or production output can skip it.
No product ranges from the sources yet.
Unknown from the sources.
4.6.3Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, a client with TCP access to an exposed Nuxt development server can send a nuxt:dev:client-error event over the HMR socket with an absolute file path at the end of its message. The development server reads that file while building the client error report and returns its contents through the error overlay, development error channel, and terminal report, bypassing Vite's server.fs allow list. The default localhost binding limits remote exposure, cross-origin browser requests are rejected, production builds and Nuxt 3 are not affected, and no browser interaction is required. This issue is fixed in version 4.6.3.
This page as .md · .json · in your agent: get_signal("CVE-2026-119198")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.