Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

Nuxt server islands render useHeadSafe input without sanitisation

CVE-2026-114133GHSA-xfq5-w38q-pc2x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nuxt 4.6.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm nuxt

    Affected
    >= 3.13.0, < 4.6.2
    Fixed in
    4.6.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2026-114133: 0.22% estimated exploitation activity in the next 30 days; percentile 12.65 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact useHeadSafe restricts head input to an allowlist of safe tags and attributes. For example, bodyAttrs is limited to class and style, event handler attributes are removed, and <script tags are only kept for JSON types. When useHeadSafe is called inside a server island (a .server.vue component or page, or a component rendered with <NuxtIsland), the island renderer serialises the raw input of every head entry into the island response without the option that marks it as safe input. <NuxtIsland then pushes that input into the page's head as a regular entry, both during server rendering and when hydrating or refetching on the client. As a result, input that useHeadSafe would normally strip (such as bodyAttrs.onload or executable <script content) is rendered into the page. If an application passes user-controlled data to useHeadSafe inside a server island, an attacker who controls that data can achieve stored cross-site scripting on the application's origin. Mitigating factors -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-xfq5-w38q-pc2x

  2. Revision 2 · amended ·

    Amended from osv record GHSA-xfq5-w38q-pc2x

  3. Revision 1 · created ·

    Published from ghsa record GHSA-xfq5-w38q-pc2x

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-114133

Advisory: Nuxt server islands render `useHeadSafe` input without sanitisation
IDs: CVE-2026-114133, GHSA-xfq5-w38q-pc2x
Record: https://patchnext.com/advisories/cve-2026-114133 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.6.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 3.13.0, < 4.6.2; fixed in 4.6.2

## Suggested inspection (read-only)
- `npm ls nuxt --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xfq5-w38q-pc2x (GitHub-reviewed advisory GHSA-xfq5-w38q-pc2x lists affected ranges: npm nuxt >=3.13.0 <4.6.2)
- Verified: https://osv.dev/vulnerability/GHSA-xfq5-w38q-pc2x (OSV record GHSA-xfq5-w38q-pc2x lists affected ranges: npm nuxt >=3.13.0 <4.6.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…