Nuxt payload URL generation has quadratic cost for repeated slashes in the request path
Published 16 Nov 2026 · Updated 16 Nov 2026
Is your project on an affected nuxt?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=4.6.0 <4.6.4
- Fixed in
- 4.6.4
npm install nuxt@4.6.4Details
Summary
Nuxt strips trailing slashes from the request path with a regular expression whose cost grows quadratically with the length of a run of consecutive slashes. A single unauthenticated request with a long run of slashes can occupy the server's event loop for a noticeable time, delaying every other request handled by the same process.
Impact
When a page is rendered with payload extraction (any route covered by an isr, swr or cache route rule), Nuxt builds the _payload.json URL from the raw request path. A path such as /blog/a followed by 16,000 slashes and x, which fits within Node's default header size limit, takes roughly 0.1 to 0.4 seconds of synchronous CPU time per request, depending on hardware. Concurrent requests to the same process wait for it to finish, so a modest request rate can keep a process saturated.
An app is affected if it uses Nuxt 4.6.0 or later with server-side rendering and has a route rule like:
export default defineNuxtConfig({
routeRules: {
'/blog/**': { swr: true },
},
})The same pattern is also reachable through the opt-in experimental.early404 option, for any request path.
Apps without isr, swr or cache route rules and without experimental.early404 are not affected, nor are fully prerendered or client-only apps. The cost is bounded by the maximum request path length, so a reverse proxy with a smaller header limit reduces it further. There is no confidentiality or integrity impact.
Patches
Fixed in nuxt 4.6.4. Trailing slashes are now removed with a linear scan instead of a regular expression.
Workarounds
Reject request paths containing repeated slashes before they reach the renderer, for example at the reverse proxy or with a server middleware:
// server/middleware/reject-repeated-slashes.ts
export default defineEventHandler((event) => {
if (event.path.split('?')[0]!.includes('//')) {
throw createError({ statusCode: 404 })
}
})If you use experimental.early404, you can also disable it until you upgrade.
Credits
Thanks to cryptofox9 for reporting this issue.
Is GHSA-r9jc-w898-3fv6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected nuxt, and gives you the command that fixes it.
More advisories for nuxt
- LowCVE-2026-128076Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342) · 16 Nov 2026
- MediumCVE-2026-128075Nuxt exposes the message and data of unhandled errors thrown during server rendering · 16 Nov 2026
- MediumCVE-2026-128071Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes · 16 Nov 2026
- MediumCVE-2026-119200Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes · 30 Oct 2026
- MediumCVE-2026-114132Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive · 22 Oct 2026
- MediumCVE-2026-114133Nuxt server islands render `useHeadSafe` input without sanitisation · 22 Oct 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.