Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Misconfiguration·Updated Nov 20, 2026

CVE-2026-119199 Scanner

CVE-2026-119199 Scanner - Information Disclosure vulnerability in Nuxt

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
4.4k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
5.9
CVSSmedium
Exploitable remotely over the internet · no authentication required.
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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
nuxtby nuxt
>= 3.0.0, < 4.6.3
Updated Nov 20, 2026View on NVD →
Detail

Nuxt is a widely-used development framework for building modern web applications. It is often used by both small startups and large companies to create powerful and scalable server-side applications. Developers leverage Nuxt for its ease of use and powerful features, which streamline the application development process. With its modular architecture, Nuxt allows for flexibility and customization to meet specific needs. Despite its robust capabilities, vulnerabilities can exist, particularly in development settings where the server might be exposed without adequate protections. Nuxt supports a vibrant community which contributes to its development and maintenance.

The information disclosure vulnerability in Nuxt pertains to the unintended exposure of sensitive runtime configuration data. This flaw exists in versions of Nuxt from 3.0.0 to 4.6.3, potentially allowing unauthorized users to access private configuration data. Such data could include sensitive information that should typically remain confidential, such as secrets. The revelation of this information could give malicious actors insights into application internals, making systems more susceptible to targeted exploitation. Understanding and addressing this type of vulnerability is crucial to maintain the security integrity of applications developed using Nuxt.

Technical details of this vulnerability involve the inappropriate inlining of private runtime configuration values into the development bundle. This is through the Nitro 2 development server, which inadvertently serves these inline configurations. The endpoint affected is accessible over HTTP via Vite file serving, where remote attackers can read exposed configurations. Critical parameters within the exposed data include "_inlineRuntimeConfig" and "buildId", which are embedded in the development index file. Such exposure signifies an exploitable weakness in the development configuration of the application.

If exploited, this vulnerability could lead to significant security breaches. Attackers who gain access to these configurations could exploit them to perform further malicious activities. They could leverage the disclosed information to navigate and manipulate the application environment. Potential misuse includes unauthorized access, privilege escalation, or further exploitation of the application's architecture. Prevention and remediation are paramount to safeguard against compromise resulting from this vulnerability.

REFERENCES

Solution Advice
  • Update Nuxt to version 4.6.3 or later to remediate the information disclosure vulnerability.
  • Implement strict firewall rules to block unauthorized HTTP requests to development servers.
  • Review and secure your server configurations to prevent unnecessary exposure of sensitive data.
  • Regularly audit your configuration files to ensure sensitive data is not inadvertently exposed.
  • Engage with community advisories and patches to stay up-to-date on security practices.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.