CVE-2026-119199

Nuxt dev server exposes private runtime config through the Nitro dev bundle

Published Oct 29, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Nuxt’s development server serves the Nitro development bundle at <buildDir>/dev/index.mjs when accessed over HTTP. The bundle contains values from runtimeConfig that are inlined at build time, including secrets set in nuxt.config as well as the automatically generated appSecret in Nuxt 4.6.0 and later. If the dev server is reachable beyond the default localhost binding, an attacker can retrieve these secrets by requesting the bundle, resulting in an unauthorized disclosure of confidential data.

Affected Systems

The vulnerability affects Nuxt versions starting from 3.0.0 up to and including 4.6.2. Production builds, Nitro 3, and runtime configuration supplied only via environment variables at startup are not impacted. The issue is fixed in Nuxt 4.6.3.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate severity. EPSS information is not available, so the precise exploitation likelihood is uncertain, though the problem is not listed in the CISA KEV catalog. The attack vector is limited to those who can reach the dev server over HTTP; the default localhost binding mitigates remote exposure, but if the server is exposed or the binding is modified, an attacker could exploit the flaw to read sensitive configuration and secrets.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Nuxt to version 4.6.3 or newer, which removes the inlining of private runtime configuration into the dev bundle.
  • Restrict the Nuxt development server to bind only to localhost (127.0.0.1) and ensure it is not exposed to external networks in production environments.
  • Disable or remove the development server from production builds and deployment pipelines to prevent exposure of debug bundles.

Generated by OpenCVE AI on October 29, 2026 at 21:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-648h-gw55-m2g7 Nuxt dev server exposes private runtime config through the Nitro dev bundle
History
Type Values Removed Values Added
First Time appeared Nuxt
Nuxt nuxt
Vendors & Products Nuxt
Nuxt nuxt
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Nuxt dev server exposes private runtime config through the Nitro dev bundle
Weaknesses CWE-200
CWE-538
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-538

    Insertion of Sensitive Information into Externally-Accessible File or Directory

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 29, 2026, 8:27 PM
Reserved
Oct 29, 2026, 4:04 PM
Status
Awaiting Analysis
Published
Oct 29, 2026, 9:17 PM
Modified
Oct 30, 2026, 5:18 PM