This is a low-severity (CVSS 3.1) origin validation flaw in the Nuxt webpack and rspack dev server builders: a malicious page opened in a developer's browser can use DNS rebinding to pass the same-origin check and read compiled client chunks, source maps, local file paths and any secrets inlined into the client bundle. It affects development machines only, not production builds or the default Vite builder, and private runtimeConfig is not exposed. EPSS is low in absolute terms (0.00136, though in the 97th percentile), there is no public exploit, no Nuclei template and no KEV listing, but the package has 6,591 downstream dependents and exploitation needs only a developer visiting a hostile page while `nuxt dev` runs. Upgrade @nuxt/webpack-builder and @nuxt/rspack-builder to 4.6.4, add any proxy hostnames to devServer.allowedHosts, and rotate any secrets that were inlined into client bundles during development. Nuxt 3 is end of life and will not be patched, so teams on it should switch to Vite or migrate.
What is the risk?
Low overall. The attack is network-reachable but needs high complexity (knowing or guessing the dev server port, timing the DNS change) and user interaction (the developer visits an attacker-controlled page). Impact is limited to low confidentiality loss with no integrity or availability effect. Chromium 142+ Local Network Access prompts further reduce exposure, while Firefox and Safari users are more exposed. Risk rises for teams that inline API keys or internal endpoints into client bundles during development, or whose AI-facing apps are built on Nuxt with the webpack or rspack builder.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| Anthropic Python | npm | >= 4.0.0, < 4.6.4 | 4.6.4 |
| Anthropic Python | npm | >= 4.0.0, < 4.6.4 | 4.6.4 |
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade @nuxt/webpack-builder and @nuxt/rspack-builder to 4.6.4 or later. 2) If the dev server is reached through a reverse proxy or another hostname, add it to devServer.allowedHosts. 3) Until patched, use the default Vite builder for development. 4) Use Chromium 142+ with Local Network Access restrictions and avoid browsing untrusted sites while the dev server runs. 5) Treat any secrets inlined into client bundles during development as exposed and rotate them. 6) Migrate off Nuxt 3, which is end of life and unpatched. 7) Detection: look for dev server requests to /_nuxt/* with unexpected Host headers, and for DNS records that flip between public and loopback addresses.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-128072?
This is a low-severity (CVSS 3.1) origin validation flaw in the Nuxt webpack and rspack dev server builders: a malicious page opened in a developer's browser can use DNS rebinding to pass the same-origin check and read compiled client chunks, source maps, local file paths and any secrets inlined into the client bundle. It affects development machines only, not production builds or the default Vite builder, and private runtimeConfig is not exposed. EPSS is low in absolute terms (0.00136, though in the 97th percentile), there is no public exploit, no Nuclei template and no KEV listing, but the package has 6,591 downstream dependents and exploitation needs only a developer visiting a hostile page while `nuxt dev` runs. Upgrade @nuxt/webpack-builder and @nuxt/rspack-builder to 4.6.4, add any proxy hostnames to devServer.allowedHosts, and rotate any secrets that were inlined into client bundles during development. Nuxt 3 is end of life and will not be patched, so teams on it should switch to Vite or migrate.
Is CVE-2026-128072 actively exploited?
No confirmed active exploitation of CVE-2026-128072 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-128072?
1) Upgrade @nuxt/webpack-builder and @nuxt/rspack-builder to 4.6.4 or later. 2) If the dev server is reached through a reverse proxy or another hostname, add it to devServer.allowedHosts. 3) Until patched, use the default Vite builder for development. 4) Use Chromium 142+ with Local Network Access restrictions and avoid browsing untrusted sites while the dev server runs. 5) Treat any secrets inlined into client bundles during development as exposed and rotate them. 6) Migrate off Nuxt 3, which is end of life and unpatched. 7) Detection: look for dev server requests to /_nuxt/* with unexpected Host headers, and for DNS records that flip between public and loopback addresses.
What systems are affected by CVE-2026-128072?
This vulnerability affects the following AI/ML architecture patterns: Web front ends for LLM applications, Developer workstations and local dev environments, Nuxt-based AI dashboards and chat interfaces.
What is the CVSS score for CVE-2026-128072?
CVE-2026-128072 has a CVSS v3.1 base score of 3.1 (LOW). The EPSS exploitation probability is 0.14%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0025Exfiltration via Cyber MeansAML.T0037Data from Local SystemAML.T0078Drive-by CompromiseCompliance Controls Affected
What are the technical details?
Original Advisory
### Summary When using the webpack or rspack builder, the dev server serves built client chunks to any request whose `Host` header matches its `Origin`/`Referer`, or that carries `Sec-Fetch-Site: same-origin`. After a DNS rebinding attack both headers name the attacker's hostname, so a malicious page opened while `nuxt dev` is running can read `/_nuxt/*.js` and exfiltrate the app's source. This bypasses the same-origin check added for [GHSA-4gf7-ff8x-hq99](https://github.com/nuxt/nuxt/security/advisories/GHSA-4gf7-ff8x-hq99), [GHSA-6m52-m754-pw2g](https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g) and [GHSA-x6qj-4h56-5rj5](https://github.com/nuxt/nuxt/security/advisories/GHSA-x6qj-4h56-5rj5). ### Impact A developer runs `nuxt dev` with `builder: 'webpack'` or `builder: 'rspack'` (the default config is enough; `--host` is not required) and opens a page on an attacker-controlled hostname, for example `http://rebind.attacker.example:3000/`. The attacker then re-points that hostname at `127.0.0.1`. Requests from the page now reach the dev server as same-origin requests: ```bash curl -H 'Host: rebind.attacker.example:3000' -H 'Sec-Fetch-Site: same-origin' http://127.0.0.1:3000/_nuxt/app.js # 200, with the compiled modules ``` The page can read the response with `fetch`, which exposes the compiled source and its inline source maps, module identifiers, the developer's local filesystem paths, and any developer-controlled values inlined into the client bundle (for example through a custom `DefinePlugin`). With rspack, the HMR websocket also accepts connections from the rebound hostname. Private `runtimeConfig` is not part of the client bundle. The attacker needs to know or guess the dev server port and to time the DNS change. Chrome 142+ and other Chromium-based browsers that enforce [Local Network Access restrictions](https://developer.chrome.com/release-notes/142#local_network_access_restrictions) prompt before a public page can reach a loopback address. The default Vite builder is not affected: Vite rejects unknown `Host` headers through `server.allowedHosts`. Production builds are not affected. ### Patches Fixed in `@nuxt/webpack-builder` 4.6.4 and `@nuxt/rspack-builder` 4.6.4. The dev middleware now rejects requests whose `Host` header is not `localhost`, `*.localhost`, an IP address, or a hostname allowed by the new `devServer.allowedHosts` option or by `vite.server.allowedHosts`, before any `Sec-Fetch-Site`/`Origin`/`Referer` checks. This includes `devServer.host` and the hosts `nuxt dev` allows for the addresses it listens on; `nuxt dev --public` allows any host, as it does with Vite. With rspack, the same list is passed to rsbuild's `server.allowedHosts`, which covers the HMR websocket. When accessing the dev server through another hostname, for example through a reverse proxy, add that hostname to `devServer.allowedHosts` (a leading `.` also allows subdomains; true allows any host). Nuxt 3 has reached end of life and will not receive a fix. ### Workarounds - Use the default Vite builder for development. - Use Chrome 142+ or another Chromium-based browser that enforces Local Network Access restrictions, and don't open untrusted sites in other browsers while the dev server is running. - Treat secrets inlined into the client bundle during development as exposed and rotate them. ### Credits Nuxt thanks Anthropic for reporting this through coordinated disclosure (ANT-2026-VKRM97G5).
Exploitation Scenario
An attacker lures a developer working on an LLM-powered Nuxt app to a page at rebind.attacker.example:3000 while `nuxt dev` is running with the webpack builder. The attacker's DNS first resolves to a public server that serves the page, then re-points to 127.0.0.1. The page's JavaScript fetches /_nuxt/app.js from what the browser considers the same origin, receives the compiled modules and inline source maps, and exfiltrates them to the attacker. The attacker then mines the source for internal API endpoints, local paths and any inlined LLM API keys for follow-on abuse.
Weaknesses (CWE)
CWE-346 — Origin Validation Error: The product does not properly verify that the source of data or communication is valid.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:NReferences
- github.com/advisories/GHSA-x2wv-5868-p7v2
- github.com/nuxt/nuxt/commit/3c9645326a2b3f5cfa09c9a935db9b1825d560e7
- github.com/nuxt/nuxt/commit/3e1c7964e6843e1c5f218867a4ccd4cd00ad9ebb
- github.com/nuxt/nuxt/commit/8c11d965dad5bfc58d4c25e796915aec045acb78
- github.com/nuxt/nuxt/commit/f8d64c9aa773a033596532365d455890da9da197
- github.com/nuxt/nuxt/releases/tag/v4.6.4
- github.com/nuxt/nuxt/security/advisories/GHSA-x2wv-5868-p7v2
- nvd.nist.gov/vuln/detail/CVE-2026-128072
Timeline
Related Vulnerabilities
CVE-2026-9460310.0Podman: checkpoint images override sandbox on run
Same package: anthropicCVE-2026-466339.8Twig: single-quote escape flaw in {% use %} allows RCE
Same package: anthropicCVE-2026-544498.8LangBot: RCE via arbitrary STDIO MCP command
Same package: anthropicCVE-2026-277758.8Gitea: cached permission check allows repo takeover
Same package: anthropicCVE-2026-75748.7Claude Desktop: VM integrity bypass enables RCE
Same package: anthropic