CVE-2026-44572

Low

Description

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.

SeverityLow
CVSS3.7
Exploit probability—
ProductVercel Next.js
PublishedMay 13, 2026
First seenMay 13, 2026
Weakness typeCWE-349CWE-349

How to fix

Update
  • vercel next.js15.5.16, 16.2.5 or later
  • next15.5.16, 16.2.5 or later

Affected products

ProductAffected versionsFixed in
vercel next.js12.2.0 ≤ v < 15.5.16, 16.0.0 ≤ v < 16.2.515.5.16, 16.2.5
nextnpm12.2.0 ≤ v < 15.5.16, 16.0.0 ≤ v < 16.2.515.5.16, 16.2.5

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.