CVE-2026-72744 json
Nuxt before 4.5.1 Information Disclosure via Chrome DevTools
published 3mo ago modified last mo. also EUVD-2026-56134 , GHSA-7c4v-fwgw-9rf7
- cvss
- 6.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm nuxt 3.21.10, 4.5.1
- nuxt nuxt 3.21.10, 4.5.1
Is CVE-2026-72744 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | 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 |
| CNA | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 4.0 | 6.9 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | nuxt | >=4.4.7, <4.5.1 >=3.21.7, <3.21.10 |
4.5.1 3.21.10 |
Affected products
- nuxt nuxt
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/nuxt/nuxt/commit/00f71bb6517abff67257c8ea1fcdc777b938b68d
web
-
github.com
/nuxt/nuxt/commit/e30c611ea03240f341fe784ab1711aa6424da2fa
web
-
github.com
/nuxt/nuxt/security/advisories/GHSA-7c4v-fwgw-9rf7
vendor-advisory, web, advisory
-
vulncheck.com
/advisories/nuxt-before-information-disclosure-via-chrome-devtools
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-72744
advisory
-
github.com
/nuxt/nuxt
package
-
github.com
/nuxt/nuxt/releases/tag/v3.21.10
web
-
github.com
/nuxt/nuxt/releases/tag/v4.5.1
web
Sources
- CVE List CVE-2026-72744
- GitHub Advisory GHSA-7c4v-fwgw-9rf7
- NVD CVE-2026-72744
- Maintainer advisory GHSA-7c4v-fwgw-9rf7
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of nuxt/nuxt published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.