Cache poisoning in Next.js

1) Race condition

EUVDB-ID: #VU109239

Risk: Low

CVSSv4.0: 1.7 [CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N/E:U/U:Clear]

CVE-ID: CVE-2025-32421

CWE-ID: CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Exploit availability: No

Description

The vulnerability allows a remote attacker to gain access to sensitive information or perform spoofing attack.

The vulnerability exists due to a race condition within the Pages Router. A remote attacker can exploit the race and obtain pageProps data instead of standard HTML code and poison the CDN cache by injecting the response body from a non-cacheable data request (?__nextDataRequest=1) into a normal request that retains cacheable headers, such as Cache-Control: public, max-age=300.

Mitigation

Install updates from vendor's website.

Vulnerable software versions

Next.js: 14.0.0 - 15.1.5

CPE2.3

• cpe:2.3:a:zeit:nextjs:14.0.0:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.0.1:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.0.2:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.0.3:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.0.4:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.1.0:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.1.1:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.1.2:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.1.3:*:*:*:*:*:*:*
• cpe:2.3:a:zeit:nextjs:14.1.4:*:*:*:*:*:*:*

External links

https://github.com/vercel/next.js/security/advisories/GHSA-qpjv-v59x-3qc4
https://vercel.com/changelog/cve-2025-32421

Q & A

Can this vulnerability be exploited remotely?

Yes. This vulnerability can be exploited by a remote non-authenticated attacker via the Internet.

Is there known malware, which exploits this vulnerability?

No. We are not aware of malware exploiting this vulnerability.