Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
Published 19 Nov 2026 · Updated 19 Nov 2026
Is your project on an affected next?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=16.0.0 <16.4.5
- Fixed in
- 16.4.5
npm install next@16.4.5- Affected
- <15.5.29
- Fixed in
- 15.5.29
npm install next@15.5.29Details
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.
Is GHSA-pc58-hwjq-p385 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected next, and gives you the command that fixes it.
More advisories for next
- MediumCVE-2026-119346Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes · 19 Nov 2026
- MediumCVE-2026-119347Next.js: SVG rejection bypass in the image optimization · 19 Nov 2026
- MediumCVE-2026-119349Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments · 19 Nov 2026
- MediumCVE-2026-119350Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params · 19 Nov 2026
- MediumCVE-2026-119351Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata · 17 Nov 2026
- MediumCVE-2026-119790Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache() · 16 Nov 2026
References
- Linkgithub.com/vercel/next.js/security/advisories/GHSA-pc58-hwjq-p385
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-119348
- Linkgithub.com/vercel/next.js/commit/2842833be3a5a1e5fef0c5fb8c96df74742eef2a
- Linkgithub.com/vercel/next.js/commit/848ec29a3fbe68c02edb022efe19b04356997c32
- Packagegithub.com/vercel/next.js
- Linkgithub.com/vercel/next.js/releases/tag/v15.5.29
- Linkgithub.com/vercel/next.js/releases/tag/v16.4.5
- Linknextjs.org/blog/november-2026-security-release
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.