https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 01 Nov 2026 13:35:18 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-119201 <p>Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, nuxt dev stores a generated appSecret in &lt;buildDir&gt;/app-secret, by default .nuxt/app-secret, within a directory allowed by Vite&#39;s server.fs configuration. A client with direct HTTP access to an exposed development server can fetch the file, use deriveSecret() to compute derived secrets such as the default useSession password, and forge session cookies accepted by that development server. The default localhost binding limits remote exposure, cross-origin browser reads are blocked, production builds and development servers with an explicitly configured appSecret are not affected. This issue is fixed in version 4.6.3.</p> <p>Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, nuxt dev stores a generated appSecret in &lt;buildDir&gt;/app-secret, by default .nuxt/app-secret, within a directory allowed by Vite&#39;s server.fs configuration. A client with direct HTTP access to an exposed development server can fetch the file, use deriveSecret() to compute derived secrets such as the default useSession password, and forge session cookies accepted by that development server. The default localhost binding limits remote exposure, cross-origin browser reads are blocked, production builds and development servers with an explicitly configured appSecret are not affected. This issue is fixed in version 4.6.3.</p> https://db.gcve.eu/vuln/fkie_cve-2026-119201 https://db.gcve.eu/vuln/ghsa-3xf4-9g3c-4h4w <p><strong>Affected:</strong> npm: @nuxt/vite-builder</p> <p>### Impact</p> <p>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 `&lt;buildDir&gt;/app-secret` (by default `.nuxt/app-secret`). The build directory is inside the directories that Nuxt passes to Vite&#39;s `server.fs.allow`, so the file can be fetched from the dev server:</p> <p>```bash curl http://&lt;dev-server&gt;/_nuxt/@fs/&lt;absolute-path-to-project&gt;/.nuxt/app-secret ```</p> <p>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.</p> <p>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&#39;s browser: Vite&#39;s CORS and host checks prevent pages on other origins from reading the response.</p> <p>Production builds never generate an `appSecret` and are not affected. Dev servers with an explicitly configured `appSecret` do not use the generated file.</p> <p>### Patches</p> <p>Fixed in `@nuxt/vite-builder` 4.6.3, which `nuxt` 4.6.3 depends on. The dev server now adds `app-secret` to Vite&#39;s `server.fs.deny`, keeping Vite&#39;s default deny list.</p> <p>### Workarounds</p> <p>Set `NUXT_APP_SECRET` in `.env` to a random value of at least 32 characters…</p> <p><strong>Affected:</strong> npm: @nuxt/vite-builder</p> <p>### Impact</p> <p>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 `&lt;buildDir&gt;/app-secret` (by default `.nuxt/app-secret`). The build directory is inside the directories that Nuxt passes to Vite&#39;s `server.fs.allow`, so the file can be fetched from the dev server:</p> <p>```bash curl http://&lt;dev-server&gt;/_nuxt/@fs/&lt;absolute-path-to-project&gt;/.nuxt/app-secret ```</p> <p>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.</p> <p>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&#39;s browser: Vite&#39;s CORS and host checks prevent pages on other origins from reading the response.</p> <p>Production builds never generate an `appSecret` and are not affected. Dev servers with an explicitly configured `appSecret` do not use the generated file.</p> <p>### Patches</p> <p>Fixed in `@nuxt/vite-builder` 4.6.3, which `nuxt` 4.6.3 depends on. The dev server now adds `app-secret` to Vite&#39;s `server.fs.deny`, keeping Vite&#39;s default deny list.</p> <p>### Workarounds</p> <p>Set `NUXT_APP_SECRET` in `.env` to a random value of at least 32 characters…</p> https://db.gcve.eu/vuln/ghsa-3xf4-9g3c-4h4w