Intel

AIKIDO-2026-634910

next is vulnerable to HTTP Response Smuggling

CVE-2026-119348Published Nov 4, 2026
November 4, 2026

63

CVE Score

Medium

HTTP Response Smuggling

Are you affected? Scan for Free

TL;DR

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.

How do I fix this?

Upgrade the next library to the patch version.

Who does this affect?

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.

Package

Versions

13.0.0 - 15.5.28

Fixed in 15.5.29

16.0.0 - 16.4.4

Fixed in 16.4.5

Background info

next is vulnerable to HTTP Response Smuggling in versions 13.0.0 - 15.5.28 and 16.0.0 - 16.4.4.

Get secure today,
quickly and for free.

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.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea