CVE-2026-119348
Next.js is a React framework for building full-stack web …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/vercel/next.js/commit/2842833be3a5a1e5fef0c5fb8c96df74742eef2a
- github.com/vercel/next.js/commit/848ec29a3fbe68c02edb022efe19b04356997c32
- github.com/vercel/next.js/releases/tag/v15.5.29
- github.com/vercel/next.js/releases/tag/v16.4.5
- github.com/vercel/next.js/security/advisories/GHSA-pc58-hwjq-p385
- nextjs.org/blog/november-2026-security-release
- nvd.nist.gov/vuln/detail/CVE-2026-119348
- github.com/advisories/GHSA-pc58-hwjq-p385
- nvd.nist.gov/vuln/detail/CVE-2026-119348
- cve.org/CVERecord?id=CVE-2026-119348
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.