CVE-2026-119201: Nuxt dev server exposes generated appSecret through Vite file serving
Impact When no appSecret is configured (via NUXTAPPSECRET, NITROAPPSECRET or runtimeConfig.appSecret), nuxt dev generates a development secret and stores it in /app-secret (by default .nuxt/app-secret). The build directory is inside the directories that Nuxt passes to Vite's server.fs.allow, so the file can be fetched from the dev server: Anyone who can read it can compute every secret derived from it with…
Published Oct 30, 2026
Affected packages
@nuxt/vite-builder
- Ecosystem
- npm
- Affected
- >= 4.6.0, < 4.6.3
- Fixed in
- 4.6.3
- Check
npm ls @nuxt/vite-builder
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
When no appSecret is configured (via NUXT_APP_SECRET, NITRO_APP_SECRET or runtimeConfig.appSecret), nuxt dev generates a development secret and stores it in <buildDir>/app-secret (by default .nuxt/app-secret). The build directory is inside the directories that Nuxt passes to Vite's server.fs.allow, so the file can be fetched from the dev server:
curl http://<dev-server>/_nuxt/@fs/<absolute-path-to-project>/.nuxt/app-secretAnyone who can read it can compute every secret derived from it with deriveSecret(), including the default password used by useSession, and so can forge session cookies accepted by that dev server.
Exploitation requires direct HTTP access to the dev server. nuxt dev listens on localhost by default, so this mainly affects dev servers that are exposed to a network (for example with --host, a published container port or a tunnel). A malicious website cannot read the file through a developer's browser: Vite's CORS and host checks prevent pages on other origins from reading the response.
Production builds never generate an appSecret and are not affected. Dev servers with an explicitly configured appSecret do not use the generated file.
Patches
Fixed in @nuxt/vite-builder 4.6.3, which nuxt 4.6.3 depends on. The dev server now adds app-secret to Vite's server.fs.deny, keeping Vite's default deny list.
Workarounds
Set NUXT_APP_SECRET in .env to a random value of at least 32 characters (for example the output of openssl rand -base64 32), or avoid exposing the dev server to untrusted networks.
If a dev server using a generated secret has been reachable by untrusted clients, delete .nuxt/app-secret (a new secret is generated on the next nuxt dev) or set NUXT_APP_SECRET. Either invalidates existing dev sessions.
Credited to Duodum.
References
- https://github.com/nuxt/nuxt/security/advisories/GHSA-3xf4-9g3c-4h4w
- https://nvd.nist.gov/vuln/detail/CVE-2026-119201
- https://github.com/nuxt/nuxt/commit/2981290f36d9c5412c022758f3d89ba21a845308
- https://github.com/nuxt/nuxt/commit/545004cc350be7003dea4116ce6206d6f980b1fd
- https://github.com/nuxt/nuxt/releases/tag/v4.6.3
- https://github.com/advisories/GHSA-3xf4-9g3c-4h4w
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. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-119198
Nuxt dev server arbitrary file read through client error reports
medium5.9Oct 30, 2026CVE-2026-119199
Nuxt dev server exposes private runtime config through the Nitro dev bundle
medium5.9Oct 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
