CVE-2026-72744

Nuxt before 4.5.1 Information Disclosure via Chrome DevTools

Published Aug 11, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Nuxt versions 4.4.7 through 4.5.0 and 3.21.7 through 3.21.9 expose the absolute filesystem path and a persistent workspace identifier via an undocumented Chrome DevTools endpoint. The flaw resides in a header‐based gate that trusts the Host header sent by the client instead of the actual source address. Because the gateway is not protected against spoofed Host headers, an unauthenticated attacker with network reach to the development server can obtain sensitive path information and identify the project with a persistent UUID, which could facilitate further attacks such as targeted exploitation or phishing. This vulnerability is classified as CWE‑200: Information Exposure.

Affected Systems

The affected systems are Nuxt projects running the development server natively. Versions prior to 4.5.1 of Nuxt 4 and prior to 3.21.10 of Nuxt 3 are vulnerable when the development server is bound to a machine‑reachable network interface and the experimental.chromeDevtoolsProjectSettings option is left at its default true value.

Risk and Exploitability

The CVSS score of 6.9 marks this flaw as moderate severity. The EPSS score is not available, and the vulnerability is not listed in the KEV catalog, suggesting that no mass exploitation is reported yet. However, the attack requires the attacker to send a crafted HTTP request on the local network, a scenario that is feasible in many development environments. Once triggered, the attacker can retrieve the project’s root directory and workspace UUID without needing authentication or browser interaction. The impact is limited to information disclosure rather than code execution, but it could nevertheless aid discovery of sensitive files and inform subsequent attacks.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Nuxt 4.5.1 or newer, or Nuxt 3.21.10 or newer, which removes the vulnerable endpoint.
  • If an upgrade is not immediately possible, disable experimental.chromeDevtoolsProjectSettings by setting it to false in nuxt.config.js to prevent the workspace endpoint from being exposed.
  • Limit the development server to localhost by running "nuxt dev --host 127.0.0.1" or by configuring a firewall to block external access to the dev server port.

Generated by OpenCVE AI on August 11, 2026 at 23:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-7c4v-fwgw-9rf7 Nuxt dev server discloses project root and workspace UUID via the Chrome DevTools workspace endpoint
History
Type Values Removed Values Added
First Time appeared Nuxt nuxt
Vendors & Products 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 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.
Title Nuxt before 4.5.1 Information Disclosure via Chrome DevTools
First Time appeared Nuxt
Nuxt nuxt\/rspack-builder
Weaknesses CWE-200
CPEs cpe:2.3:a:nuxt:nuxt\/rspack-builder:*:*:*:*:*:node.js:*:*
Vendors & Products Nuxt
Nuxt nuxt\/rspack-builder
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 11, 2026, 5:50 PM
Reserved
Aug 10, 2026, 1:53 PM
Status
Awaiting Analysis
Published
Aug 11, 2026, 1:19 PM
Modified
Sep 24, 2026, 8:44 PM