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.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | nuxt | >= 4.6.0, < 4.6.4 | 4.6.4 |
References
- CVSS vector
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- Weakness (CWE)
CWE-1333- Platform
- npm
- Package
nuxt- Disclosed
- 16.11.2026
- Updated
- 16.11.2026 17:17
Sources and licenses
OSV / GitHub Advisory Database - GHSA-r9jc-w898-3fv6 - CC BY 4.0
Vulnerability history: nuxt
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 30
- First → latest
- 06.2023 11.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 2
- High 7
- Medium 15
- Low 6
Disclosures per year
- 2023: 1
- 2024: 2
- 2025: 2
- 2026: 25
-
Nuxt payload URL generation has quadratic cost for repeated slashes in the request path this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.