CVE-2026-128072: nuxt · Origin Validation Error
Affects nuxtSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low : upgrade to 4.6.4 when convenient.
Data as of 13 Nov 2026, 17:49 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 3.1 |
|---|
- Patch
- Available – fixed in 4.6.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade nuxt and webpack-builder and rspack-builder to 4.6.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nuxtnuxt | Affected
| Fixed in
|
| @nuxtwebpack-builder | Affected
| Fixed in
|
| @nuxtrspack-builder | Affected
| Fixed in
|
AI-suggested
Upgrade Nuxt to version 4.6.4 or later, where this origin validation issue is fixed. No other mitigation is required as the vulnerability is specific to affected development middleware versions. Production builds and the default Vite builder are not affected.
Description
A vulnerability in Nuxt development middleware versions from 3.0.0 and 3.12.2 up to but not including 4.6.4 allows an attacker to bypass origin validation under specific conditions. This issue arises when the Host header names an attacker-controlled hostname, which after DNS rebinding resolves to a loopback address. An attacker can then access client JavaScript chunks and inline source maps, potentially exposing compiled source code, local filesystem paths, and developer-controlled values. The vulnerability requires the attacker to know or guess the development server port and trick the developer into opening a malicious page. The default Vite builder and production builds are not affected. The issue is fixed in Nuxt version 4.6.4.
References
- github.com/nuxt/nuxt/security/advisories/GHSA-x2wv-5868-p7v2 (opens in a new tab)
- github.com/nuxt/nuxt/commit/3c9645326a2b3f5cfa09c9a935db9b1825d560e7 (opens in a new tab)
- github.com/nuxt/nuxt/commit/3e1c7964e6843e1c5f218867a4ccd4cd00ad9ebb (opens in a new tab)
- github.com/nuxt/nuxt/commit/8c11d965dad5bfc58d4c25e796915aec045acb78 (opens in a new tab)
- github.com/nuxt/nuxt/commit/f8d64c9aa773a033596532365d455890da9da197 (opens in a new tab)
- github.com/nuxt/nuxt/releases/tag/v4.6.4 (opens in a new tab)