The Nuxt team has released Nuxt 4.5.1 and 3.21.10, along with @nuxt/devtools 3.3.1, to address eight security advisories, including a high-severity server-side remote code execution vulnerability.

Copy link to headingVulnerabilities addressed

Copy link to headingVercel platform protections

Vercel received advance notice of the server-side remote code execution vulnerability, GHSA-9473-5f9j-94wq, and deployed platform-wide WAF mitigations before public disclosure.

Applications deployed on Vercel are automatically protected by these mitigations, with no configuration changes required. However, do not rely on them for full protection. Upgrading to a patched version is still required.

The WAF mitigations cover only direct exploitation of the server-side RCE. The remaining component-instantiation, caching, authorization, denial-of-service, and development-time vulnerabilities require upgrading Nuxt and Nuxt DevTools.

Copy link to headingRecommended action

All Nuxt users should upgrade as soon as possible:

  • Nuxt 4: 4.5.1 or later

  • Nuxt 3: 3.21.10 or later

  • Nuxt DevTools: 3.3.1 or later

To upgrade, run:

npx nuxt upgrade --dedupe

Upgrading to the latest patched Nuxt release

This also refreshes the lockfile, pulling in the patched Nuxt DevTools version.

Users who previously upgraded for the earlier route rule advisory, CVE-2026-53721, must still upgrade. The newly disclosed authorization bypass is a regression in that earlier fix.

Nuxt 4 users who cache authenticated pages containing user-specific data should also follow Nuxt’s guidance and purge any upstream caches that may still contain payloads generated before the fix.

Vercel platform protections provide an additional layer of defense, but they are not a replacement for upgrading affected dependencies.

Read the Nuxt security announcement for affected configurations and complete remediation guidance.