Skip to content

Next.js Race Condition to Cache Poisoning

Low severity GitHub Reviewed Published May 14, 2025 in vercel/next.js • Updated May 15, 2025

Package

npm next (npm)

Affected versions

< 14.2.24
>= 15.0.0, < 15.1.6

Patched versions

14.2.24
15.1.6

Description

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

Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.

References

@aaronbrown-vercel aaronbrown-vercel published to vercel/next.js May 14, 2025
Published by the National Vulnerability Database May 14, 2025
Published to the GitHub Advisory Database May 15, 2025
Reviewed May 15, 2025
Last updated May 15, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(8th percentile)

Weaknesses

CVE ID

CVE-2025-32421

GHSA ID

GHSA-qpjv-v59x-3qc4

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.