Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in next 15.5.29 and next 16.4.5.
Next.js is a React framework for building full-stack web applications. Prior to 15.5.29 and 16.4.5, self-hosted Next.js App Router route handlers and the fetch cache that return a fetched upstream response unchanged can emit a response whose declared framing does not match the body actually sent. When the application is behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients. The resulting desynchronization can inject a response into another client's queue or disclose another client's response. This issue is fixed in versions 16.4.5 and 15.5.29.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| vercel | <15.5.29, >=16.0.0 <16.4.5 | ||
| npm: next | <15.5.29, <=15.5.28, >=16.0.0 <16.4.5, >=16.0.0 <=16.4.4 | 15.5.29, 16.4.5 |
Exploit evidence
1 public sources
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in next (npm), strongest first
Embed
A live severity badge for an advisory, README or ticket