CVE-2026-128074: 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.
Published Nov 16, 2026
Affected packages
nuxt
- Ecosystem
- npm
- Affected
- >= 4.6.0, < 4.6.4
- Fixed in
- 4.6.4
- Check
npm ls nuxt
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-128071
Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes
medium6.5No fixNov 16, 2026CVE-2026-128075
Nuxt exposes the message and data of unhandled errors thrown during server rendering
medium5.3No fixNov 16, 2026CVE-2026-128076
Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)
low3.1No fixNov 16, 2026CVE-2026-119200
Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes
medium6.5Oct 30, 2026CVE-2026-114130
Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabled
low2.3Oct 22, 2026CVE-2026-114131
Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routes
medium6.5Oct 22, 2026
