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.
Server-side remote code execution via server island props
Unauthorized component instantiation via server island props
Route rule authorization bypass
Server component denial of service
GHSA-hxcr-hm88-mpq6 , GHSA-9pgf-384g-p7mv
Cross-user disclosure of cached payloads, affecting Nuxt 4.x versions 4.4.0 and later
Development server path disclosure
Remote code execution in Nuxt DevTools, development-only, fixed in @nuxt/devtools 3.3.1
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.
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
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.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
