Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
GHSA-pc58-hwjq-p385 · CVE-2026-119348
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
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.
References
- WEB https://github.com/vercel/next.js/security/advisories/GHSA-pc58-hwjq-p385
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-119348
- WEB https://github.com/vercel/next.js/commit/2842833be3a5a1e5fef0c5fb8c96df74742eef2a
- WEB https://github.com/vercel/next.js/commit/848ec29a3fbe68c02edb022efe19b04356997c32
- PACKAGE https://github.com/vercel/next.js
- WEB https://github.com/vercel/next.js/releases/tag/v15.5.29
- WEB https://github.com/vercel/next.js/releases/tag/v16.4.5
- WEB https://nextjs.org/blog/november-2026-security-release
Ready to move
Start Securing
Free, no credit card | First findings in minutes