{"dataType":"CVE_RECORD","dataVersion":"5.1","cveMetadata":{"cveId":"CVE-2025-32421","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2025-04-08T10:54:58.366Z","datePublished":"2025-05-14T22:56:45.624Z","dateUpdated":"2025-05-15T15:42:26.847Z"},"containers":{"cna":{"title":"Next.js Race Condition to Cache Poisoning","problemTypes":[{"descriptions":[{"cweId":"CWE-362","lang":"en","description":"CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')","type":"CWE"}]}],"metrics":[{"cvssV3_1":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":3.7,"baseSeverity":"LOW","confidentialityImpact":"LOW","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"}}],"references":[{"name":"https://github.com/vercel/next.js/security/advisories/GHSA-qpjv-v59x-3qc4","tags":["x_refsource_CONFIRM"],"url":"https://github.com/vercel/next.js/security/advisories/GHSA-qpjv-v59x-3qc4"},{"name":"https://vercel.com/changelog/cve-2025-32421","tags":["x_refsource_MISC"],"url":"https://vercel.com/changelog/cve-2025-32421"}],"affected":[{"vendor":"vercel","product":"next.js","versions":[{"version":"< 14.2.24","status":"affected"},{"version":">= 15.0.0, < 15.1.6","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2025-05-14T22:56:45.624Z"},"descriptions":[{"lang":"en","value":"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."}],"source":{"advisory":"GHSA-qpjv-v59x-3qc4","discovery":"UNKNOWN"}},"adp":[{"metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2025-05-15T15:40:39.864352Z","id":"CVE-2025-32421","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"title":"CISA ADP Vulnrichment","providerMetadata":{"orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP","dateUpdated":"2025-05-15T15:42:26.847Z"}}]}}