GHSA-5j59-xgg2-r9c4 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up

• npm next: >= 13.3.1-canary.0, < 14.2.35 → fixed in 14.2.35 • npm next: >= 15.0.6, < 15.0.7 → fixed in 15.0.7 • npm next: >= 15.1.10, < 15.1.11 → fixed in 15.1.11 • npm next: >= 15.2.7, < 15.2.8 → fixed in 15.2.8 • npm next: >= 15.3.7, < 15.3.8 → fixed in 15.3.8 • npm next: >= 15.4.9, < 15.4.10 → fixed in 15.4.10 • npm next: >= 15.5.8, < 15.5.9 → fixed in 15.5.9 • npm next: >= 15.6.0-canary.59, < 15.6.0-canary.60 → fixed in 15.6.0-canary.60 • npm next: >= 16.0.9, < 16.0.10 → fixed in 16.0.10 • npm next: >= 16.1.0-canary.17, < 16.1.0-canary.19 → fixed in 16.1.0-canary.19

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.