CVE-2026-44572 Details
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.
A denial-of-service vulnerability has been identified in Next.js versions 12.2.0 prior to 15.5.16 and 16.0.0 prior to 16.2.5. The issue arises when an external client sends a request with the 'x-nextjs-data' header to a path managed by middleware that performs redirects. In such cases, the middleware may misinterpret the request as a data request and substitute the standard 'Location' header with the internal 'x-nextjs-redirect' header, which browsers do not recognize. If the application is behind a CDN or reverse proxy that caches 3xx responses without considering this header, an attacker could poison the cached redirect response. This would result in subsequent visitors receiving a redirect response lacking a 'Location' header, causing a denial-of-service condition on that redirect path until the cache entry expired or was cleared.
Users can upgrade to Next.js versions 15.5.16 or 16.2.5 to address this vulnerability. Before upgrading, it is recommended to configure the CDN or reverse proxy to vary its cache key on 'x-nextjs-data' for affected responses.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 14, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq | [email protected] | MitigationVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-349 | Acceptance of Extraneous Untrusted Data With Trusted Data | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| vercel next.js | >= 12.2.0, < 15.5.16 >= 16.0.0, < 16.2.5 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 15, 2026 | Initial Analysis | [email protected] |
| May 13, 2026 | New CVE Received | [email protected] |