GHSA-3G8H-86W9-WVMQ
Next.js's Middleware / Proxy redirects can be cache-poisoned
Texto original en inglés · Ver en español
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 15.5.16 | next · -5 d desde divulgación | |
| Remediación | Parche 16.2.5 | next · -5 d desde divulgación | |
| Divulgación | Publicada | GHSA-3G8H-86W9-WVMQ divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
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:
- use middleware or proxy redirects
- are deployed behind a caching CDN or reverse proxy
- allow 3xx responses on those paths to be cached without differentiating internal data requests from normal requests
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:
- configuring the CDN or reverse proxy to vary its cache key on `x-nextjs-data` for affected responses
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npmnext |
Corregida | 15.5.16, 16.2.5 | -5 d · -5 d | 16.4.6 no afectada |
15.5.1616.2.5Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-44572https://github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmqhttps://github.com/vercel/next.jshttps://github.com/vercel/next.js/releases/tag/v15.5.16https://github.com/vercel/next.js/releases/tag/v16.2.5Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
