CVE-2026-119348: Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.5.29 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.4.5
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
The issue affects self-hosted Next.js applications using App Router route handlers or the fetch cache that return a fetched upstream response unchanged. Exploitation additionally requires an HTTP/1.1 reverse proxy that permits pipelined response queueing.
What does an attacker need to exploit it?
An attacker needs a way to cause or supply a crafted upstream response that produces a mismatch between the declared response framing and the body sent. The vulnerable application must forward that fetched response unchanged through the affected deployment path.
What is the potential impact?
Response desynchronization between clients can allow a response to be injected into another client's response queue or disclose one client's response to another client.
How can this be remediated?
Upgrade Next.js to version 15.5.29 or 16.4.5, which contain the fix. The provided information does not specify a workaround for deployments that cannot be upgraded immediately.