{"id":"CVE-2026-128072","aliases":["GHSA-x2wv-5868-p7v2"],"url":"https://o3.security/vulnerability/CVE-2026-128072","summary":"@nuxt/webpack-builder and @nuxt/rspack-builder dev server serves built source to DNS rebinding pages","details":"### Summary\n\nWhen 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).\n\n### Impact\n\nA 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:\n\n```bash\ncurl -H 'Host: rebind.attacker.example:3000' -H 'Sec-Fetch-Site: same-origin' http://127.0.0.1:3000/_nuxt/app.js\n# 200, with the compiled modules\n```\n\nThe 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.\n\nThe 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.\n\nThe default Vite builder is not affected: Vite rejects unknown `Host` headers through `server.allowedHosts`. Production builds are not affected.\n\n### Patches\n\nFixed 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.\n\nWhen 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).\n\nNuxt 3 has reached end of life and will not receive a fix.\n\n### Workarounds \n\n- Use the default Vite builder for development.\n- 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.\n- Treat secrets inlined into the client bundle during development as exposed and rotate them.\n\n### Credits\n\nNuxt thanks Anthropic for reporting this through coordinated disclosure (ANT-2026-VKRM97G5).","published":"2026-11-13T17:28:20.202Z","modified":"2026-11-17T20:45:47.948516482Z","cvss":{"score":3.1,"severity":"LOW","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N"},"epss":{"score":0.00136,"percentile":0.0309,"asOf":"2026-11-16"},"cisaKev":null,"exploitsKnown":0,"affectedPackages":[{"ecosystem":"npm","name":"@nuxt/webpack-builder","fixedVersion":"4.6.4"},{"ecosystem":"npm","name":"@nuxt/webpack-builder","fixedVersion":null},{"ecosystem":"npm","name":"@nuxt/rspack-builder","fixedVersion":"4.6.4"},{"ecosystem":"npm","name":"@nuxt/rspack-builder","fixedVersion":null}],"fix":{"url":"https://github.com/nuxt/nuxt/commit/3c9645326a2b3f5cfa09c9a935db9b1825d560e7","label":"nuxt/nuxt@3c96453"},"references":[{"type":"WEB","url":"https://github.com/nuxt/nuxt/releases/tag/v4.6.4"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/128xxx/CVE-2026-128072.json"},{"type":"ADVISORY","url":"https://github.com/nuxt/nuxt/security/advisories/GHSA-x2wv-5868-p7v2"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-128072"},{"type":"FIX","url":"https://github.com/nuxt/nuxt/commit/3c9645326a2b3f5cfa09c9a935db9b1825d560e7"},{"type":"FIX","url":"https://github.com/nuxt/nuxt/commit/3e1c7964e6843e1c5f218867a4ccd4cd00ad9ebb"},{"type":"FIX","url":"https://github.com/nuxt/nuxt/commit/8c11d965dad5bfc58d4c25e796915aec045acb78"},{"type":"FIX","url":"https://github.com/nuxt/nuxt/commit/f8d64c9aa773a033596532365d455890da9da197"},{"type":"PACKAGE","url":"https://github.com/nuxt/nuxt"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-11-17T20:45:47.948516482Z"}}