next
Affected
- introduced
13.3.1-canary.0, fixed14.2.35(semver)
Fixed versions
14.2.35
Fix
- Fixed version
14.2.35npm install [email protected]
Advisory
Also known as: None
Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
It was discovered that the fix for CVE-2025-55184 in React Server Components was incomplete and did not fully mitigate denial-of-service conditions across all payload types. As a result, certain crafted inputs could still trigger excessive resource consumption.
This vulnerability affects React versions 19.0.2, 19.1.3, and 19.2.2, as well as frameworks that bundle or depend on these versions, including Next.js 13.x, 14.x, 15.x, and 16.x when using the App Router. The issue is tracked upstream as CVE-2025-67779.
A malicious actor can send a specially crafted HTTP request to a Server Function endpoint that, when deserialized, causes the React Server Components runtime to enter an infinite loop. This can lead to sustained CPU consumption and cause the affected server process to become unresponsive, resulting in a denial-of-service condition in unpatched environments.
High Basis: The source's own band: HIGH
13.3.1-canary.0, fixed 14.2.35 (semver)14.2.35
14.2.35npm install [email protected]15.0.6, fixed 15.0.7 (semver)15.0.7
15.0.7npm install [email protected]15.1.10, fixed 15.1.11 (semver)15.1.11
15.1.11npm install [email protected]15.2.7, fixed 15.2.8 (semver)15.2.8
15.2.8npm install [email protected]15.3.7, fixed 15.3.8 (semver)15.3.8
15.3.8npm install [email protected]15.4.9, fixed 15.4.10 (semver)15.4.10
15.4.10npm install [email protected]15.5.8, fixed 15.5.9 (semver)15.5.9
15.5.9npm install [email protected]15.6.0-canary.59, fixed 15.6.0-canary.60 (semver)15.6.0-canary.60
15.6.0-canary.60npm install [email protected]16.0.9, fixed 16.0.10 (semver)16.0.10
16.0.10npm install [email protected]16.1.0-canary.17, fixed 16.1.0-canary.19 (semver)16.1.0-canary.19
16.1.0-canary.19npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0