Read the docs

Nuxt server islands render unsanitized useHeadSafe input

Priority LOW 24CWE-79Published · Updated

Key facts

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

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

Summary

Nuxt, an open-source Vue.js framework, is affected from 3.13.0 before 4.6.2. The server-island renderer serializes raw useHeadSafe input without keeping its safe-input marker, so NuxtIsland inserts that input into the page head as an ordinary entry, which enables cross-site scripting (CWE-79). An attacker who can supply data passed to useHeadSafe in a server component or a component rendered through NuxtIsland can store script in the application origin, and a user must interact with the page for it to run.

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. From 3.13.0 until 4.6.2, the server-island renderer serializes raw useHeadSafe entry input into the island response without preserving the safe-input marker, and NuxtIsland later inserts that input into the page head as an ordinary entry. An application that passes attacker-controlled data to useHeadSafe in a .server.vue component or page, or in a component rendered through NuxtIsland, can therefore render values normally removed by the allowlist, including event-handler attributes or executable script content, resulting in stored cross-site scripting in the application origin. This issue is fixed in version 4.6.2 .

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0022 12th percentileScored 2026-11-07
Fix Fixed nuxt (nuxt): 4.6.2nuxt (npm): 4.6.2

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
nuxtnuxt3.13.0 to before 4.6.24.6.2Patch availableCNA
—nuxt (npm)3.13.0 to before 4.6.24.6.2Patch availableGHSA-xfq5-w38q-pc2x
  • nuxt Vendornuxt Affected 3.13.0 to before 4.6.2 Fixed in 4.6.2 Patch available CNA
  • nuxt (npm) Vendor— Affected 3.13.0 to before 4.6.2 Fixed in 4.6.2 Patch available GHSA-xfq5-w38q-pc2x

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.2, the listed fixed version.

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

  • Fix · CNA nuxt (nuxt) Fixed in 4.6.2
  • Fix · GHSA-xfq5-w38q-pc2x nuxt (npm) Fixed in 4.6.2 Advisory →

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-114133
  2. 2026-10-22 Alias added: GHSA-xfq5-w38q-pc2x
  3. 2026-10-22 Fix available: npm/[email protected] · GHSA-xfq5-w38q-pc2x
  4. 2026-10-22 CVSS score added · GHSA-xfq5-w38q-pc2x
  5. 2026-10-22 Weakness changed · GHSA-xfq5-w38q-pc2x
  6. 2026-10-22 5 new references · GHSA-xfq5-w38q-pc2x
  7. 2026-10-23 Priority changed: MEDIUM → LOW
  8. 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