CVE-2026-72744: Nuxt before 4.5.1 Information Disclosure via Chrome DevTools
Nuxt versions >= 4.4.7 and < 4.5.1, and >= 3.21.7 and < 3.21.10, contain an information disclosure vulnerability in the development server's Chrome DevTools workspace endpoint (GET /.well-known/appspecific/com.chrome.devtools.json). The endpoint's local-request gate (isLocalDevRequest) is header-based and trusts the attacker-supplied Host header rather than the connected peer address. When the dev server is bound to a network-reachable interface (e.g. nuxt dev --host) and experimental.chromeDevtoolsProjectSettings is enabled (the default), an unauthenticated attacker on the LAN can send a request with a spoofed Host header and no browser-specific headers (Sec-Fetch-Site, Origin, Referer) to retrieve the project's absolute filesystem root path (rootDir) and a persistent per-project workspace UUID. Production builds are unaffected. Fixed in 4.5.1 and 3.21.10.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.5.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.21.10 - Configuration
Disable experimental.chromeDevtoolsProjectSettings so the development server's Chrome DevTools workspace endpoint is not exposed via the /.well-known/appspecific/com.chrome.devtools.json route.
Nuxt development server experimental.chromeDevtoolsProjectSettings = disabled - Compensating control
Do not bind the Nuxt dev server to a network-reachable interface (avoid nuxt dev --host). Restrict access to the dev server to trusted networks/hosts only so unauthenticated LAN attackers cannot reach the Chrome DevTools workspace endpoint.