CVE-2026-119348mediumCWE-444

CVE-2026-119348: medium-severity vulnerability in vercel next.js

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

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

33Vexday Risk Score

No sign of exploitation. It has a public proof of concept.

ssvc Attendcvss 6.3epss 0.5%
from disclosure to weapon4 days
Published on NVDNov 16
1st PoC+4d
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.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
vercel · next.js
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.