next
Affected
- introduced
12.2.0, fixed15.5.16(semver)
Fixed versions
15.5.16
Fix
- Fixed version
15.5.16npm install [email protected]
Advisory
Also known as: CVE-2026-44572
Next.js's Middleware / Proxy redirects can be cache-poisoned
Impact
Next.js uses the x-nextjs-data request header for internal data requests. On affected versions, an external client could send this 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.
Affected scenarios
This affects applications that:
Fix
The fix stops trusting x-nextjs-data by itself for middleware redirect handling. A request is now treated as an internal data request only when it is validated as such by internal routing state, preserving legitimate data-request redirect behavior while preventing external header injection from changing normal redirect responses.
Workarounds
Before upgrading, users can reduce risk by:
x-nextjs-data for affected responsesLow Basis: The source's own band: LOW
12.2.0, fixed 15.5.16 (semver)15.5.16
15.5.16npm install [email protected]16.0.0, fixed 16.2.5 (semver)16.2.5
16.2.5npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0