Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
Affected releases · next
- 16.x16.0.9Fixed in 16.0.10
- 15.x15.0.6 – 15.5.8Fixed in 15.5.9
- 14.x14.0.0 – 14.2.34Fixed in 14.2.35
- 13.x13.3.1 – 13.5.11No fix on this line yet
On 16.x, the newest line:
npm install next@16.0.10Not affected
16.0.0 – 16.0.8
9 releases
Affected
16.0.9
1 release
Fixed
16.0.10 – 16.4.2
35 releases, latest
Not affected
15.0.0 – 15.0.5
6 releases
Affected
15.0.6
1 release
Fixed
15.0.7 – 15.1.9
12 releases
Affected
15.1.10
1 release
Fixed
15.1.11 – 15.2.6
9 releases
Affected
15.2.7
1 release
Fixed
15.2.8 – 15.3.6
9 releases
Affected
15.3.7
1 release
Fixed
15.3.8 – 15.4.8
11 releases
Affected
15.4.9
1 release
Fixed
15.4.10 – 15.5.7
10 releases
Affected
15.5.8
1 release
Fixed
15.5.9 – 15.5.28
19 releases
Affected
14.0.0 – 14.2.34
45 releases
Fixed
14.2.35
1 release
Not affected
13.0.0 – 13.3.0
21 releases
Affected
13.3.1 – 13.5.11
35 releases
Is your project affected?
Paste your package.json, or type the range you declare for next. It is read in your browser and sent nowhere.
What happens
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.