# CVE-2026-72744: Nuxt before 4.5.1 Information Disclosure via Chrome DevTools

> An attacker on the LAN can spoof headers to leak project paths and UUIDs from the Nuxt dev server if bound to a network interface.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-7c4v-fwgw-9rf7

## What is CVE-2026-72744?

CVE-2026-72744 is a medium-severity vulnerability in nuxt, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-72744?

4 open source packages ship an affected version, including nuxt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt` | npm | From 3.21.7 | 3.21.10 |
| `nuxt` | npm | From 3.21.7 | 3.21.10 |
| `nuxt` | npm | From 4.4.7 | 4.5.1 |
| `nuxt` | npm | From 4.4.7 | 4.5.1 |

## How do I fix CVE-2026-72744?

Upgrade nuxt to a fixed version for your release line: 3.21.10 or 4.5.1.

## Is CVE-2026-72744 being exploited?

There is no known exploitation of CVE-2026-72744 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Saku0512/CVE-2026-72744-poc (github_poc): https://github.com/Saku0512/CVE-2026-72744-poc

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72744 and fix it if it is affected.

What it is: CVE-2026-72744 is a medium-severity vulnerability in nuxt, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72744 in the wild and no public exploit code.

Affected packages and fixed versions:
- nuxt (npm): affected from 3.21.7; fixed in 3.21.10
- nuxt (npm): affected from 3.21.7; fixed in 3.21.10
- nuxt (npm): affected from 4.4.7; fixed in 4.5.1
- nuxt (npm): affected from 4.4.7; fixed in 4.5.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72744/ (Markdown: https://insights.sbomify.com/CVE-2026-72744/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72744
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72744
- OSV: https://osv.dev/vulnerability/CVE-2026-72744

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72744/
Summaries are generated and may contain mistakes; the official description above is the record.