Advisory

GHSA-9pgf-384g-p7mv

Also known as: CVE-2026-71321

Summary

Nuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validation

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-08-05 21:43 UTC
Modified
2026-08-05 21:55 UTC

Affected packages and fixes

nuxt

npm · All systems

Affected

  • introduced 4.0.0, fixed 4.5.1 (semver)

Fixed versions

4.5.1

Fix

nuxt

npm · All systems

Affected

  • introduced 3.1.0, fixed 3.21.10 (semver)

Fixed versions

3.21.10

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences