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: bash curl http:// /nuxt/@fs/ /.nuxt/app-secret Anyone 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…

curl https://cve.zerocrew.in/api/cve/CVE-2026-119201