Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-x2wv-5868-p7v2

LowCVSS 3.1 / 10
Published Nov 16, 2026·Last modified Nov 16, 2026
Affected Components(4)
npm logo@nuxt/rspack-builder
4.0.0 – 4.6.4
npm logo@nuxt/webpack-builder
4.0.0 – 4.6.4
npm logo@nuxt/webpack-builder
>= 3.0.0
1 / 2
Description

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, GHSA-6m52-m754-pw2g and 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:

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 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).

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
3.1

The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information.

Threat Intelligence
2.9

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
0.14%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard