Technical impact
This vulnerability in self‑hosted Next.js allows a malicious upstream response to be inserted into or disclosed from another client's response stream. The flaw arises when route handlers or the fetch cache return a fetched upstream response unchanged, causing the declared framing to mismatch the actual body when the application sits behind an HTTP/1.1 reverse proxy that supports pipelined queues. Because the response framing differs, a crafted upstream payload can desynchronize the client queues, leading to injection of forged responses or inadvertent leakage of relative client data. The weakness is classified as CWE‑444: Response Injection, providing a pathway for an attacker to manipulate cross‑client HTTP responses without authentication or privilege escalation.
Affected Systems
Vercel’s Next.js framework, specifically self‑hosted deployments of the App Router route handlers and fetch cache before version 15.5.29 and 16.4.5, are affected. Any next.js app running in those versions and exposed to an HTTP/1.1 reverse proxy that allows pipelining is vulnerable; older or patched versions are not.
Risk and Exploitability
The CVSS score of 6.3 indicates medium severity. Because the EPSS score is not available and the issue is not listed in the CISA KEV catalog, direct exploitation data is limited, but the attack path is clear: an attacker must control or influence an upstream response that travels through the application, and the application must be behind a reverse proxy permitting request pipelining. Once these conditions are met, the attacker can inject crafted headers and body content into the next client in the pipeline or read data intended for another client, thereby achieving information disclosure or tampering with client traffic. The risk is therefore contingent on the presence of the specific proxy configuration.