Is CVE-2026-119199 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-119199 being exploited in the wild.

How severe is CVE-2026-119199?

Medium severity, with a CVSS score of 5.9, published 29 October 2026.

Which products and versions are affected?

@nuxt/vite-builder (npm) >= 3.0.0, < 4.6.3, SEMVER:introduced=3.0.0,fixed=4.6.3; Nuxt 3.0.0 to 4.6.2.

How is CVE-2026-119199 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-119199?

Check whether you run @nuxt/vite-builder (npm) or Nuxt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119199: Nuxt development server secrets exposure in bundled configuration

Q: Is there a fix for CVE-2026-119199?

Yes. @nuxt/vite-builder (npm): upgrade to 4.6.3 or later. Until then: Do not expose the Nuxt development server to untrusted networks; bind it to localhost only or use a firewall to restrict access to trusted development machines. Avoid committing secrets to nuxt.config; use NUXT_* environment variables at server startup instead, as these are not inlined into the bundle. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-119199 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-119199?

Check whether you run @nuxt/vite-builder (npm) or Nuxt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119199 · Severity: medium · CVSS 5.9 · Published 2026-10-29

Nuxt, a web development framework for Vue.js, exposes sensitive secrets and configuration values through its development server when accessed over HTTP. An attacker who can reach the development server can retrieve private API keys, database credentials, and other secrets that were compiled into the development bundle. This vulnerability only affects development environments and does not impact production deployments or the latest Nitro 3 runtime.

Technologies: @nuxt/vite-builder (npm), Nuxt. Vendors: npm, Nuxt.

Quick answers

Is CVE-2026-119199 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119199 being exploited in the wild.
How severe is CVE-2026-119199?: Medium severity, with a CVSS score of 5.9, published 29 October 2026.
Which products and versions are affected?: @nuxt/vite-builder (npm) >= 3.0.0, < 4.6.3, SEMVER:introduced=3.0.0,fixed=4.6.3; Nuxt 3.0.0 to 4.6.2.
Is there a fix for CVE-2026-119199?: Yes. @nuxt/vite-builder (npm): upgrade to 4.6.3 or later. Until then: Do not expose the Nuxt development server to untrusted networks; bind it to localhost only or use a firewall to restrict access to trusted development machines. Avoid committing secrets to nuxt.config; use NUXT_* environment variables at server startup instead, as these are not inlined into the bundle. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-119199 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-119199?: Check whether you run @nuxt/vite-builder (npm) or Nuxt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@nuxt/vite-builder (npm): upgrade to 4.6.3 or later
```
npm install @nuxt/vite-builder@4.6.3
```

Do not expose the Nuxt development server to untrusted networks; bind it to localhost only or use a firewall to restrict access to trusted development machines. Avoid committing secrets to nuxt.config; use NUXT_* environment variables at server startup instead, as these are not inlined into the bundle.

Technical details

The Nuxt development server exposes the Nitro 2 development bundle at <buildDir>/dev/index.mjs via Vite file serving. Private runtimeConfig values from nuxt.config and generated appSecrets (in version 4.6.0+) are inlined into this bundle at build time. An attacker with network access to the dev server can retrieve this file and extract embedded secrets. Environment variables supplied at runtime via NUXT_* variables are not affected, and the default localhost binding limits exposure unless the dev server is explicitly bound to external interfaces.

Affected products

Nuxt Nuxt 3.0.0 to 4.6.2

Identifiers

CVE-2026-119199
GHSA-648h-gw55-m2g7

Timeline

2026-10-29: disclosed
2026-10-27: patched: Version 4.6.3 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.