CVE-2026-71321: Nuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validation
Impact The internal island renderer endpoint (/nuxtisland/...) decodes and hashes attacker-controlled request input before it validates the URL-resident hash. An unauthenticated POST /nuxtisland/ .json with a large JSON body (for example ~4.6 MB / 150k keys) is fully read, destr-parsed, and run through ohash before the request is rejected with a 400.
Published Aug 5, 2026
Affected packages
nuxt
- Ecosystem
- npm
- Affected
- >= 4.0.0, < 4.5.1
- Fixed in
- 4.5.1
- Check
npm ls nuxt
nuxt
- Ecosystem
- npm
- Affected
- >= 3.1.0, < 3.21.10
- Fixed in
- 3.21.10
- Check
npm ls nuxt
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The internal island renderer endpoint (/__nuxt_island/...) decodes and hashes attacker-controlled request input before it validates the URL-resident hash. An unauthenticated POST /__nuxt_island/<name>_<anything>.json with a large JSON body (for example ~4.6 MB / 150k keys) is fully read, destr-parsed, and run through ohash before the request is rejected with a 400. Because Nitro runs on a single event loop, this both wastes CPU on the doomed request and delays every concurrent request. A low request rate is enough to degrade or stall the server. No valid hash and no authentication are required.
Patches
Fixed in [email protected] and [email protected]. The island handler now enforces a raw body-size cap (413) and a JSON nesting-depth cap (400) before parsing or hashing, so oversized or deeply nested input is rejected cheaply.
Workarounds
Put a small request-body limit in front of /__nuxt_island/ at your reverse proxy / edge (islands legitimately send only a compact props payload), or disable server components if unused.
Credited to dinhvaren.
References
- https://github.com/nuxt/nuxt/security/advisories/GHSA-9pgf-384g-p7mv
- https://github.com/nuxt/nuxt/commit/4e35ae9babd94be53246e31200232d48438bb34e
- https://github.com/nuxt/nuxt/commit/668cdfdfda41849ed11c1ee5e2067a11fc103b22
- https://github.com/nuxt/nuxt/releases/tag/v3.21.10
- https://github.com/nuxt/nuxt/releases/tag/v4.5.1
- https://github.com/advisories/GHSA-9pgf-384g-p7mv
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-128071
Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes
medium6.5No fixNov 16, 2026CVE-2026-128074
Nuxt payload URL generation has quadratic cost for repeated slashes in the request path
medium6.9Nov 16, 2026CVE-2026-128075
Nuxt exposes the message and data of unhandled errors thrown during server rendering
medium5.3No fixNov 16, 2026CVE-2026-128076
Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)
low3.1No fixNov 16, 2026CVE-2026-119200
Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes
medium6.5Oct 30, 2026CVE-2026-114130
Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabled
low2.3Oct 22, 2026
