CVE-2026-44572— Next.js 安全漏洞

Next.js: Middleware / Proxy redirects can be cache-poisoned

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.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

在可信数据中接受外来的不可信数据

Next.js 安全漏洞

Next.js是Vercel开源的一个 React 框架。 Next.js 12.2.0至15.5.16之前版本和16.2.5之前版本存在安全漏洞，该漏洞源于外部客户端可在由返回重定向的中间件处理的正常请求上发送x-nextjs-data标头，可能导致后续访问者收到无Location标头的缓存重定向响应，造成拒绝服务。

N/A

N/A