next is vulnerable to HTTP Response Smuggling
63
CVE Score
Medium
HTTP Response Smuggling
Self-hosted next applications that return a fetched upstream response unchanged from App Router route handlers or the fetch cache can emit a response whose declared framing does not match the body actually sent. When the application sits behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients. This allows an attacker to inject responses to other clients and disclose other clients' responses.
Upgrade the next library to the patch version.
You are affected if you are using a version that falls within the vulnerable range, self-host your application, return a fetched upstream response unchanged from an App Router route handler or the fetch cache, and run it behind an HTTP/1.1 reverse proxy that permits pipelined response queueing.
13.0.0 - 15.5.28
Fixed in 15.5.2916.0.0 - 16.4.4
Fixed in 16.4.5next is vulnerable to HTTP Response Smuggling in versions 13.0.0 - 15.5.28 and 16.0.0 - 16.4.4.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.