Next.js Race Condition to Cache Poisoning

THẤP 3.7CVE-2025-32421 · GHSA-qpjv-v59x-3qc4 · Công bố 14/05/2025 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2025-32421 là lỗ hổng mức THẤP (CVSS 3.7) ảnh hưởng next.js (vercel), next.
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.80%, cao hơn 56.8% các lỗ hổng khác.
Cách xử lý: cập nhật lên 15.1.6, 14.2.24 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
next.js vercel	`≥ 15.0.0, < 15.1.6< 14.2.24`	`15.1.614.2.24`
next npm	`≥ 0.9.9, < 14.2.24≥ 15.0.0, < 15.1.6`	`14.2.2415.1.6`

Mô tả

Summary
We received a responsible disclosure from Allam Rachid (zhero) for a low-severity race-condition vulnerability in Next.js. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve pageProps data instead of standard HTML.

Learn more here

Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.

Mô tả của NVD

Next.js is a React framework for building full-stack web applications. Versions prior to 14.2.24 and 15.1.6 have a race-condition vulnerability. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve `pageProps` data instead of standard HTML. This issue was patched in versions 15.1.6 and 14.2.24 by stripping the `x-now-route-matches` header from incoming requests. Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on `200 OK` status without explicit `cache-control` headers. Those who self-host Next.js deployments and are unable to upgrade immediately can mitigate this vulnerability by stripping the `x-now-route-matches` header from all incoming requests at the content development network and setting `cache-control: no-store` for all responses under risk. The maintainers of Next.js strongly recommend only caching responses with explicit cache-control headers.