Skip to main content
VulnerabilityPublished

CVE-2026-128077: nuxt · Interpretation Conflict

Affects nuxtSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.6.4 when convenient.

Data as of 13 Nov 2026, 17:49 UTC

CVSS 3.1 base score
6.5Medium
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.16.5
Patch
Available – fixed in 4.6.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 nitro-server to 4.6.4.

Affected software

ProductAffectedFixed in
nuxtnuxtAffected
  • >=4.6.0 <4.6.4
Fixed in
  • 4.6.4
@nuxtnitro-serverAffected
  • >=4.6.0 <4.6.4
Fixed in
  • 4.6.4

AI-suggested

Upgrade Nuxt to version 4.6.4 or later, where this URL interpretation conflict is fixed. No other mitigation is necessary as the vendor has provided an official fix.

Description

Nuxt versions from 4.6.0 up to but not including 4.6.4 have a URL interpretation conflict where request paths starting with // are parsed differently by Nuxt and Nitro server components. This discrepancy allows unauthenticated requests like //x/admin to bypass route-scoped server handlers, middleware path checks, redirects, and security headers configured for the /admin route. The issue is fixed in version 4.6.4.

References

Community reviews

Loading reviews…