Servers and applications
GHSA-m3q2-p4fw-w38m
Cross-site scripting via <NoScript> slot content in Nuxt's head components
- Severity
- Low 2.3
- Published
- 2 Jun 2026
- Last changed
- 2 Jun 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.21.7, 4.4.7
- Weakness
- Cross-site scripting (CWE-79)
- Attack
- Over the network · Only under certain conditions · No login needed · Needs someone to view a page or file
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
Nuxt's globally registered component (from @unhead/vue head components, re-exported by Nuxt) wrote its default-slot content to the innerHTML of the head tag, bypassing the HTML escaping that {{ }} interpolation normally applies in Vue templates.
Applications that placed untrusted, attacker-controllable data inside a slot, for example:
would emit that value unescaped inside in the server-rendered HTML. With scripting enabled, the HTML parser treats content in under the "in head noscript" insertion mode: any tag other than link, meta, noframes, or style implicitly closes and is re-processed in the head. A payload such as `
` therefore escapes the element and executes in the document context.
Sibling head components (, ) were not affected because they already routed slot text through the safe textContent path.
Workarounds
Until you can upgrade:
- Do not interpolate untrusted input into slots. Replace {{ x }} with a static string, or sanitise / HTML-escape x` at the source.
- If you must render dynamic noscript content, write the tag yourself via useHead({ noscript: [{ textContent: escapedValue }] }) after escaping escapedValue.
Affected software
| Software | Affected versions |
|---|---|
NuxtServers and applications · github:nuxt/nuxt |
|
About Nuxt
JavaScript framework
- Developers who used it in the past year
- 4%Stack Overflow Developer Survey 2025, 2025
- Weekly downloads (npm)
- 3,404,733npm, 15 Nov 2026
- GitHub stars
- 61,078GitHub, 15 Nov 2026
- Forks
- 5,837GitHub, 15 Nov 2026
- Latest release
- v4.6.4GitHub, 15 Nov 2026
- Released
- 2 Nov 2026GitHub
- License
- MIT LicenseWikidata
- Written in
- JavaScript, Vue.jsWikidata
- First published on GitHub
- 26 Oct 2016GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4 | 4.6.4 | Yes |
| 3 | 3.21.11 | Ended 31 Jul 2026 |
| 2 | 2.18.1 | Ended 30 Jun 2024 |
| 1 | 1.4.5 | Ended 21 Sept 2019 |
From endoflife.date.
Vulnerabilities in Nuxt
- In our list
- 49
- Published in the last 12 months
- 46
- Critical, last 12 months
- 1
- High, last 12 months
- 8
- Known exploited
- 0
- CVE-2023-54417Nuxt 3.0.0 < 3.4.2 Unauthenticated File Read via vite-node Dev ServerHigh 8.7 18 Nov 2026
- CVE-2023-54418Nuxt 3.0.0-rc.1 < 3.0.0-rc.13 Unauthenticated Arbitrary File Read via Vite Dev ServerHigh 8.7 18 Nov 2026
- GHSA-r99w-jh2x-3mg9Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routesMedium 6.5 2 Nov 2026
- CVE-2026-128077Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routesMedium 6.5 2 Nov 2026
- GHSA-hf59-9xwc-2g4pColliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)Low 3.1 2 Nov 2026
- CVE-2026-128076Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)Low 3.1 2 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-m3q2-p4fw-w38m
- github.com https://github.com/nuxt/nuxt/security/advisories/GHSA-m3q2-p4fw-w38m