- Severity: LOW
- CVE: CVE-2026-128072
- Ecosystems: npm, npm, npm, npm
- Packages: @nuxt/webpack-builder, @nuxt/webpack-builder, @nuxt/rspack-builder, @nuxt/rspack-builder
### 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 (…
Source: GitHub Security Advisories · 2026-11-16