CVE-2026-44572
Next.js is a React framework for building full-stack web …
Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, an external client could send a x-nextjs-data header on a normal request to a path handled by middleware that returns a redirect. When that happened, the middleware/proxy could treat the request as a data request and replace the standard Location redirect header with the internal x-nextjs-redirect header. Browsers do not follow x-nextjs-redirect, so the response became an unusable redirect for normal clients. If the application was deployed behind a CDN or reverse proxy that caches 3xx responses without varying on this header, a single attacker request could poison the cached redirect response for the affected path. Subsequent visitors could then receive a cached redirect response without a Location header, causing a denial of service for that redirect path until the cache entry expired or was purged. This vulnerability is fixed in 15.5.16 and 16.2.5.
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/security/advisories/GHSA-3g8h-86w9-wvmq
- github.com/vercel/next.js/releases/tag/v15.5.16
- github.com/vercel/next.js/releases/tag/v16.2.5
- github.com/advisories/GHSA-3g8h-86w9-wvmq
- nvd.nist.gov/vuln/detail/CVE-2026-44572
- nvd.nist.gov/vuln/detail/CVE-2026-44572
- cve.org/CVERecord?id=CVE-2026-44572
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.