CVE-2025-32421
published 2025-05-14CVE-2025-32421: 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…
PriorityP416low3.7CVSS 3.1
AVNACHPRNUINSUCLINAN
EPSS
0.67%
47.1th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| next | next | >= 0.9.9 < 14.2.24 | 14.2.24 |
| next | next | >= 15.0.0 < 15.1.6 | 15.1.6 |
| vercel | next.js | < 14.2.24 | 14.2.24 |
| vercel | next.js | — | — |
| vercel | next.js | >= 15.0.0 < 15.1.6 | 15.1.6 |
CVSS provenance
nvdv3.13.7LOWCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
vendor_redhat3.7LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Next.js Race Condition to Cache Poisoning
osv·2025-05-15
CVE-2025-32421 [LOW] Next.js Race Condition to Cache Poisoning
Next.js Race Condition to Cache Poisoning
**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](https://vercel.com/changelog/cve-2025-32421)
**Credit**
Thank you to **Allam Rachid (zhero)** for the responsible disclosure. This research was rewarded as part of our bug bounty program.
GHSA
Next.js Race Condition to Cache Poisoning
ghsa·2025-05-15
CVE-2025-32421 [LOW] CWE-362 Next.js Race Condition to Cache Poisoning
Next.js Race Condition to Cache Poisoning
**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](https://vercel.com/changelog/cve-2025-32421)
**Credit**
Thank you to **Allam Rachid (zhero)** for the responsible disclosure. This research was rewarded as part of our bug bounty program.
Red Hat
next.js: Next.js Race Condition to Cache Poisoning
vendor_redhat·2025-05-14·CVSS 3.7
CVE-2025-32421 [LOW] CWE-362 next.js: Next.js Race Condition to Cache Poisoning
next.js: Next.js Race Condition to Cache Poisoning
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-
No detection rules found.
No public exploits indexed.
2025-05-14
Published