Skip to main content
VulnerabilityPublished

CVE-2026-119199: nuxt · Information Exposure

Affects nuxtSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 4.6.3 when convenient.

Data as of 29 Oct 2026, 20:59 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.9
Patch
Available – fixed in 4.6.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade nuxt and nuxt/nuxt to 4.6.3.

Affected software

ProductAffectedFixed in
nuxtnuxtAffected
  • >=3.0.0 <4.6.3
Fixed in
  • 4.6.3
GitHubnuxt/nuxtpkg:github/nuxt/nuxtOther threatsAffected
  • >=3.0.0 <4.6.3
Fixed in
  • 4.6.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Nuxt to version 4.6.3 or later, where this issue is fixed. Avoid exposing the development server over HTTP to untrusted networks. Production builds and Nitro 3 are not affected, so using production builds or upgrading to Nitro 3 can also mitigate the risk.

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.

References

Community reviews

Loading reviews…