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.
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Paczka npm | nuxt | >= 4.6.0, < 4.6.4 | 4.6.4 |
Odnośniki
- Wektor 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- Słabość (CWE)
CWE-1333- Platforma
- npm
- Paczka
nuxt- Ujawniono
- 16.11.2026
- Aktualizacja
- 16.11.2026 17:17
Źródła i licencje
OSV / GitHub Advisory Database - GHSA-r9jc-w898-3fv6 - CC BY 4.0
Historia podatności: nuxt
Wszystkie opisane podatności tej paczki (Paczka npm), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 30
- Pierwsza → ostatnia
- 06.2023 11.2026
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Krytyczna 2
- Wysoka 7
- Średnia 15
- Niska 6
Ujawnienia w latach
- 2023: 1
- 2024: 2
- 2025: 2
- 2026: 25
-
Nuxt payload URL generation has quadratic cost for repeated slashes in the request path ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.