NetSight
medium6.3

CVE-2026-119348

Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses

Impact

Self-hosted Next.js applications (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 such an application sits behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients, enabling response injection and disclosure of other clients' responses.

An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data being read, low risk of data or systems being changed.

Affected packages

EcosystemPackageAffectedFixed in
npmnext>= 16.0.0, <= 16.4.416.4.5

Affected products · Vercel

ProductAffected versions
Next.js
before 15.5.29
from 16.0.0, before 16.4.5
Version < 15.5.29

Weakness classification

References