Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
vercel next.js
< 15.5.29affected>= 16.0.0, < 16.4.5affected
References
- https://github.com/vercel/next.js/security/advisories/GHSA-pc58-hwjq-p385 ↗
- https://github.com/vercel/next.js/commit/2842833be3a5a1e5fef0c5fb8c96df74742eef2a ↗
- https://github.com/vercel/next.js/commit/848ec29a3fbe68c02edb022efe19b04356997c32 ↗
- https://github.com/vercel/next.js/releases/tag/v15.5.29 ↗
- https://github.com/vercel/next.js/releases/tag/v16.4.5 ↗
- https://nextjs.org/blog/november-2026-security-release ↗