CVE-2026-44572
EUVD-2026-3005113.05.2026, 16:16
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.Enginsight
Affected Products (NVD)
| Vendor | Product | Version |
|---|---|---|
| vercel | next.js | 12.2.0 ≤ 𝑥 < 15.5.16 |
| vercel | next.js | 16.0.0 ≤ 𝑥 < 16.2.5 |
𝑥
= Vulnerable software versions
Common Weakness Enumeration