# CVE-2026-44572

## Summary

- **CVE ID:** CVE-2026-44572
- **Severity:** LOW
- **CVSS Score:** 3.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L)
- **CWE:** CWE-349
- **Published:** May 13, 2026
- **Last Modified:** May 14, 2026

## 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.

## Affected Products

- vercel — next.js (>= 12.2.0, < 15.5.16)
- vercel — next.js (>= 16.0.0, < 16.2.5)

## References

- [CNA](https://github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq)

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.30%
- **EPSS Percentile:** 22.3

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-11._