Nuxt July 2026 security advisory
Mirrored from Vercel — AI for archival readability. Support the source by reading on the original site.
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.
Vulnerabilities addressed
Vulnerability | Severity | Advisory |
|---|---|---|
Server-side remote code execution via server island props | High | |
Unauthorized component instantiation via server island props | Medium | |
Route rule authorization bypass | High | |
Server component denial of service | High | |
Cross-user disclosure of cached payloads, affecting Nuxt 4.x versions 4.4.0 and later | High | |
Development server path disclosure | Low | |
Remote code execution in Nuxt DevTools, development-only, fixed in | Critical |
Vercel 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.
Recommended action
All Nuxt users should upgrade as soon as possible:
Nuxt 4:
4.5.1or laterNuxt 3:
3.21.10or laterNuxt DevTools:
3.3.1or later
To upgrade, run:
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.
Discussion (0)
Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.
Sign in →No comments yet. Sign in and be the first to say something.