CVE-2026-119348 in Next.js
Summary
by MITRE • 11/16/2026
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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/16/2026
Next.js serves as a prominent React framework designed for constructing full-stack web applications, offering developers robust tools for server-side rendering and static site generation. Within this ecosystem, the App Router provides mechanisms for defining route handlers that can interact with external services or upstream APIs. A critical security flaw was identified in versions prior to 15.5.29 and 16.4.5 concerning how these route handlers manage HTTP responses when they act as proxies for fetched upstream data. Specifically, the vulnerability arises when a Next.js application fetches a response from an upstream server and returns it unchanged to the client without properly validating or adjusting the framing headers relative to the actual body content being transmitted.
The technical core of this vulnerability lies in a mismatch between the declared HTTP framing and the actual bytes sent over the wire. When a route handler retrieves data from an external source, it may inherit response headers such as Content-Length that do not accurately reflect the length of the body if the upstream server employs chunked transfer encoding or other dynamic framing methods without proper conversion by Next.js. This discrepancy creates a situation where the HTTP parser on either side of the connection cannot correctly delineate message boundaries. In standard single-client scenarios, this might result in minor parsing errors or dropped connections, but the severity escalates significantly when the application is deployed behind an HTTP/1.1 reverse proxy that supports pipelined response queueing.
HTTP/1.1 request pipelining allows multiple requests to be sent over a single TCP connection without waiting for individual responses, relying on precise framing to ensure each response corresponds correctly to its originating request. If the Next.js application sends a malformed or desynchronized response due to the aforementioned header-body mismatch, it can disrupt this queueing mechanism. A crafted upstream response that exploits this flaw can cause the reverse proxy or client HTTP parser to misinterpret where one response ends and another begins. This desynchronization effectively allows an attacker who controls the upstream service to inject their own malicious responses into the stream intended for other legitimate clients or to intercept and disclose sensitive data belonging to those clients by manipulating the boundary markers of the HTTP messages.
The operational impact of this vulnerability is severe, primarily categorized under CWE-20: Improper Input Validation, as the framework fails to adequately validate the integrity of upstream response headers before relaying them. Furthermore, the ability to inject responses into another client's queue aligns with MITRE ATT&CK techniques related to HTTP Response Splitting and Server-Side Request Forgery implications, although it is distinct in its reliance on pipelining desynchronization rather than header injection for cache poisoning or XSS. This flaw enables potential data leakage of private user information and can lead to cross-user response contamination, undermining the confidentiality and integrity guarantees expected from secure web applications.
To mitigate this risk, organizations running self-hosted Next.js instances must immediately upgrade to version 15.5.29 or later for the LTS branch, or version 16.4.5 and above for newer releases. These patched versions include corrections that ensure proper handling of upstream response framing, preventing the desynchronization issue from occurring. Additionally, administrators should consider disabling HTTP/1.1 pipelining on their reverse proxies if possible, as this protocol feature is rarely used in modern web traffic and its removal eliminates the specific vector required for exploiting this vulnerability. Regularly updating dependencies and monitoring for new CVEs related to framework internals remains a critical component of maintaining a secure application infrastructure.