Next.js Race Condition to Cache Poisoning
Description
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 packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
nextnpm | >= 0.9.9, < 14.2.24 | 14.2.24 |
nextnpm | >= 15.0.0, < 15.1.6 | 15.1.6 |
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4- github.com/advisories/GHSA-qpjv-v59x-3qc4ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2025-32421ghsaADVISORY
- github.com/vercel/next.js/security/advisories/GHSA-qpjv-v59x-3qc4ghsax_refsource_CONFIRMWEB
- vercel.com/changelog/cve-2025-32421ghsax_refsource_MISCWEB
News mentions
0No linked articles in our index yet.