Read the docs

Nuxt development server exposes private runtime config in dev bundle

Priority LOW 26CWE-200Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-200.

Summary

Nuxt versions from 3.0.0 before 4.6.3 are affected. The development server serves the Nitro development bundle, which inlines private runtimeConfig secrets and, from 4.6.0, the generated development appSecret (CWE-200). A remote attacker who can reach the dev server over HTTP can read these values without privileges. The default localhost binding limits remote exposure, and production builds are not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-10-31

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0035 28th percentileScored 2026-11-07
Fix Fixed nuxt (nuxt): 4.6.3@nuxt/vite-builder (npm): 4.6.3

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
nuxtnuxt3.0.0 to before 4.6.34.6.3Patch availableCNA
—@nuxt/vite-builder (npm)3.0.0 to before 4.6.34.6.3Patch availableGHSA-648h-gw55-m2g7
  • nuxt Vendornuxt Affected 3.0.0 to before 4.6.3 Fixed in 4.6.3 Patch available CNA
  • @nuxt/vite-builder (npm) Vendor— Affected 3.0.0 to before 4.6.3 Fixed in 4.6.3 Patch available GHSA-648h-gw55-m2g7

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:*——nuxt
  • cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:* Versions — — ·nuxt

Remediation

Upgrade @nuxt/vite-builder to version 4.6.3. The sources list no fixed version for nuxt.

Written with Claude Haiku 5.5 from the sources below · 2026-10-31

  • Fix · CNA nuxt (nuxt) Fixed in 4.6.3
  • Fix · GHSA-648h-gw55-m2g7 @nuxt/vite-builder (npm) Fixed in 4.6.3 Advisory →

Timeline

  1. 2026-10-29 Threatist record created from CVE-2026-119199
  2. 2026-10-30 Alias added: GHSA-648h-gw55-m2g7
  3. 2026-10-30 Fix available: npm/@nuxt/[email protected] · GHSA-648h-gw55-m2g7
  4. 2026-10-30 CVSS score added · GHSA-648h-gw55-m2g7
  5. 2026-10-30 Weakness changed · GHSA-648h-gw55-m2g7
  6. 2026-10-30 5 new references · GHSA-648h-gw55-m2g7

References

  • TI-2023-03020 Code Injection in nuxt/nuxt CVSS 3.1CRITICAL 9.8
  • TI-2024-28339 Server-Side Request Forgery (SSRF) in nuxt-icon CVSS 3.1HIGH 8.6
  • TI-2024-22685 Remote code execution via the browser when running the test locally in nuxt CVSS 3.1HIGH 8.8
  • TI-2026-26689 Nuxt OG Image vulnerable to DoS via image generation CVSS 4.0MEDIUM 6.9
  • TI-2022-04037 Cross-site Scripting (XSS) - DOM in nuxt/framework CVSS 3.1MEDIUM 6.1
  • TI-2022-04036 Cross-site Scripting (XSS) - Reflected in nuxt/framework CVSS 3.1MEDIUM 6.1
See all 44 →

Sources