Nuxt payload URL generation has quadratic cost for repeated slashes in the request path
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.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | nuxt | >= 4.6.0, < 4.6.4 | 4.6.4 |
Referencias
- Vector CVSS
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N- Debilidad (CWE)
CWE-1333- Plataforma
- npm
- Paquete
nuxt- Publicada
- 16.11.2026
- Actualizado
- 16.11.2026 17:17
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-r9jc-w898-3fv6 - CC BY 4.0
Historial de vulnerabilidades: nuxt
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 30
- Primera → última
- 06.2023 11.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 2
- Alta 7
- Media 15
- Baja 6
Divulgaciones por año
- 2023: 1
- 2024: 2
- 2025: 2
- 2026: 25
-
Nuxt payload URL generation has quadratic cost for repeated slashes in the request path esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.