
We found results for “”
CVE-2025-32421
Good to know:

Date: May 14, 2025
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.
Severity Score
Severity Score
Weakness Type (CWE)
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-362Top Fix

Upgrade Version
Upgrade to version next - 15.1.6;next - 14.2.24;next - 14.2.24;https://github.com/vercel/next.js.git - v15.1.6;https://github.com/vercel/next.js.git - v14.2.24
CVSS v3.1
Base Score: |
|
---|---|
Attack Vector (AV): | NETWORK |
Attack Complexity (AC): | HIGH |
Privileges Required (PR): | NONE |
User Interaction (UI): | NONE |
Scope (S): | UNCHANGED |
Confidentiality (C): | LOW |
Integrity (I): | NONE |
Availability (A): | NONE |