vercel · Next.js · published 2026-05-13
CVE-2026-44572Next.js: Middleware / Proxy redirects can be cache-poisoned
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-44572 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 23% of all CVEs. This Next.js vulnerability: CVSS 3.7 (v3.1). Fixed upstream in Next.js 16.2.5, 15.5.16. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Next.js 16.2.5, 15.5.16.
Patch events
Web frameworkNext.js
Next.js security releases: 16.2.5, 15.5.16
Upgrade to
16.2.515.5.16Why: CVE-2026-44578: EPSS 36% with high severity (CVSS 8.6).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (23th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 3.7 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vercel next.js
>= 12.2.0, < 15.5.16(affected)>= 16.0.0, < 16.2.5(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.