Skip to main content
← All vulnerabilities
CVE-2026-119201EUVD-2026-113372GHSA-3XF4-9G3C-4H4W

Nuxt dev server exposes generated appSecret through Vite file serving

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.6.3
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Nuxt, a Vue.js web development framework, is affected when its development server (`nuxt dev`) is reachable over the network, because it can expose a generated secret file that lets an attacker forge session cookies accepted by that dev server. Production builds and dev servers with a manually configured secret are not affected, and the default localhost binding and browser cross-origin protections limit exposure.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

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 <buildDir>/app-secret, by default .nuxt/app-secret, within a directory allowed by Vite'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.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • nuxt nuxt

    From 4.6.0 · fixed in 4.6.3

References 4

GitHub · nuxt/nuxt