Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1amended

Nuxt: Reflected XSS in via unsanitised javascript: or data: URL

CVE-2026-53722GHSA-934w-87qh-qr26

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nuxt 4.4.7, 3.21.7), 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
    >= 4.0.0, < 4.4.7>= 3.0.0, < 3.21.7
    Fixed in
    4.4.7, 3.21.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-53722: 0.29% estimated exploitation activity in the next 30 days; percentile 21.96 (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.

Summary <NuxtLink did not validate the URL scheme of values bound to its to or href props before rendering them into the href attribute of the underlying <a element. When an application binds attacker-controlled input (a query parameter, a CMS field, a user-supplied profile URL) to <NuxtLink :to or :href, the attacker can supply a javascript: or vbscript: URL that is reflected verbatim into the rendered markup. Clicking the link executes the supplied script in the origin of the Nuxt application, resulting in reflected DOM-based cross-site scripting. A data:text/html,... payload reflected through the same sink does not execute in the application's origin but enables a same-tab phishing surface anchored to a legitimate application link. The same value was exposed to consumers of the component's custom slot via the href and route.href props, so applications that re-bind those values to their own anchors were affected identically. Unlike the previously reported navigateTo issue…

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

    Amended from ghsa record GHSA-934w-87qh-qr26

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-934w-87qh-qr26

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-53722

Advisory: Nuxt: Reflected XSS in ` ` via unsanitised `javascript:` or `data:` URL
IDs: CVE-2026-53722, GHSA-934w-87qh-qr26
Record: https://patchnext.com/advisories/cve-2026-53722 (revision 3, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.4.7, 3.21.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 4.0.0, < 4.4.7; >= 3.0.0, < 3.21.7; fixed in 4.4.7, 3.21.7

## 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://osv.dev/vulnerability/GHSA-934w-87qh-qr26 (OSV record GHSA-934w-87qh-qr26 lists affected ranges: npm nuxt >=4.0.0 =3.0.0 <3.21.7 (fixed))
- Verified: https://github.com/advisories/GHSA-934w-87qh-qr26 (GitHub-reviewed advisory GHSA-934w-87qh-qr26 lists affected ranges: npm nuxt >=4.0.0 =3.0.0 <3.21.7)

Commands are suggestions: review each one before running it.

Loading voting…