NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
LOW severity

CVE-2026-128072 — @nuxt/webpack-builder

LOWFix: nuxt/nuxt@3c96453

CVE-2026-128072 is a low-severity (CVSS 3.1) CWE-346 vulnerability in @nuxt/webpack-builder. A fix is available for @nuxt/webpack-builder — see the affected versions and patch details below.

@nuxt/webpack-builder and @nuxt/rspack-builder dev server serves built source to DNS rebinding pages

Also known asGHSA-x2wv-5868-p7v2
Published
Updated
Affected
4 pkgs
Patched
2 / 4
Exploits
None indexed
Exploitation data as of Nov 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-128072.

EPSS Exploitation Probability

via FIRST.org ↗
0.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@nuxt/webpack-buildernpm
2Kdownloads / week
@nuxt/rspack-buildernpm
698downloads / week

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

Affected Packages

4 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npm@nuxt/webpack-builder≥ 4.0.0&&< 4.6.44.6.4npm install @nuxt/webpack-builder@4.6.4
📦npm@nuxt/webpack-builder≥ 3.0.0No fix
📦npm@nuxt/rspack-builder≥ 4.0.0&&< 4.6.44.6.4npm install @nuxt/rspack-builder@4.6.4
📦npm@nuxt/rspack-builder≥ 3.12.2No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nuxt/webpack-builder, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @nuxt/webpack-builder to 4.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-128072 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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/advisor
O3 Security · Impact-Aware SCA

Is CVE-2026-128072 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2026-128072: @nuxt/webpack-builder — Fixed in 4.6.4