Skip to main content
VulnerabilityPublished

CVE-2026-128072: nuxt · Origin Validation Error

Affects nuxtSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.13.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
nuxtnuxtAffected
  • >=3.0.0 <4.6.4
Fixed in
  • 4.6.4
@nuxtwebpack-builderAffected
  • >=3.0.0 <4.6.4
Fixed in
  • 4.6.4
@nuxtrspack-builderAffected
  • >=3.12.2 <4.6.4
Fixed in
  • 4.6.4

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

Community reviews

Loading reviews…