Read the docs

Incomplete fix lets Nuxt NuxtLink render javascript: URLs

Priority LOW 12CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Passive
Attack complexity
Low
Attack requirements
Present
Impact type
Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-79.

Summary

Nuxt versions before 4.6.0 are affected when the pages feature is disabled. An incomplete fix for an earlier issue lets attacker-controlled input bound to the to attribute of NuxtLink, prefixed with an ASCII control character, be rendered as a javascript: href, which is cross-site scripting (CWE-79). A remote attacker can run script in the application's origin if a victim clicks the crafted link.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

Nuxt is an open-source web development framework for Vue.js. Prior to 4.6.0, an incomplete fix for CVE-2026-53722 allows an application with pages disabled to render a script-capable URL through NuxtLink when attacker-controlled input bound to to is prefixed with an ASCII C0 control character. The no-pages router classifies the value as an internal route before the earlier protocol check and passes it to the rendered anchor href; browsers remove the leading control character and interpret the remaining javascript: URL. The default anchor and NuxtLink custom output are affected, the unsafe href is present in server-rendered HTML, and a victim must click the link for script to execute in the application's origin. This issue is fixed in version 4.6.0.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00406 35th percentileScored 2026-11-07
Fix Fixed nuxt (nuxt): 4.6.0nuxt (npm): 4.6.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
nuxtnuxtbefore 4.6.04.6.0Patch availableCNA
—nuxt (npm)before 4.6.04.6.0Patch availableGHSA-jjm6-p2m9-9w4x
  • nuxt Vendornuxt Affected before 4.6.0 Fixed in 4.6.0 Patch available CNA
  • nuxt (npm) Vendor— Affected before 4.6.0 Fixed in 4.6.0 Patch available GHSA-jjm6-p2m9-9w4x

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:*——nuxt
  • cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:* Versions — — ·nuxt

Remediation

Upgrade the nuxt npm package to version 4.6.0, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA nuxt (nuxt) Fixed in 4.6.0
  • Fix · GHSA-jjm6-p2m9-9w4x nuxt (npm) Fixed in 4.6.0 Advisory →

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-114130
  2. 2026-10-22 Alias added: GHSA-jjm6-p2m9-9w4x
  3. 2026-10-22 Fix available: npm/[email protected] · GHSA-jjm6-p2m9-9w4x
  4. 2026-10-22 CVSS score added · GHSA-jjm6-p2m9-9w4x
  5. 2026-10-22 Weakness changed · GHSA-jjm6-p2m9-9w4x
  6. 2026-10-22 7 new references · GHSA-jjm6-p2m9-9w4x
  7. 2026-10-28 CISA SSVC decision points changed

References

  • TI-2023-03020 Code Injection in nuxt/nuxt CVSS 3.1CRITICAL 9.8
  • TI-2024-28339 Server-Side Request Forgery (SSRF) in nuxt-icon CVSS 3.1HIGH 8.6
  • TI-2024-22685 Remote code execution via the browser when running the test locally in nuxt CVSS 3.1HIGH 8.8
  • TI-2026-26689 Nuxt OG Image vulnerable to DoS via image generation CVSS 4.0MEDIUM 6.9
  • TI-2022-04037 Cross-site Scripting (XSS) - DOM in nuxt/framework CVSS 3.1MEDIUM 6.1
  • TI-2022-04036 Cross-site Scripting (XSS) - Reflected in nuxt/framework CVSS 3.1MEDIUM 6.1
See all 44 →

Sources