CVE-2026-119348
Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
Description
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.
INFO
Published Date :
Nov. 16, 2026, 6:43 p.m.
Last Modified :
Nov. 16, 2026, 6:43 p.m.
Remotely Exploit :
No
Source :
GitHub_M
Solution
- Update Next.js to version 16.4.5 or later.
- Update Next.js to version 15.5.29 or later.
- Ensure HTTP/1.1 reverse proxy does not queue pipelined responses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-119348 vulnerability anywhere in the article.