Live › vulnerability › CVE-2026-119199
The Nuxt development server can serve its Nitro development bundle over HTTP, which contains private runtimeConfig values set in nuxt.config, including secrets. An attacker who can reach the dev server can read those secrets, and on Nuxt 4.6.0 and later also the generated development appSecret.
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 development server (not production builds) with a version from 3.0.0 through 4.6.2 that is reachable over HTTP and has private secrets in nuxt.config runtimeConfig. The default localhost binding limits remote exposure, production builds and Nitro 3 are not affected, and secrets supplied only via NUXT_* environment variables at startup are not inlined.
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 3.0.0 until 4.6.3, the Nuxt development server can expose the Nitro 2 development bundle at <buildDir>/dev/index.mjs through Vite file serving when the server is reachable over HTTP. Nitro inlines private runtimeConfig values resolved at build time into that bundle, including secrets configured in nuxt.config, and Nuxt 4.6.0 and later also inline the generated development appSecret. The default localhost binding limits remote exposure, production builds and Nitro 3 are not affected, and runtime configuration supplied only through NUXT_* environment variables at server startup is not inlined. This issue is fixed in version 4.6.3.
This page as .md · .json · in your agent: get_signal("CVE-2026-119199")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.