Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
Published 12 Dec 2025 · Updated 10 Sept 2026
Affected packages
- Affected
- >=13.3.1-canary.0 <14.2.35
- Fixed in
- 14.2.35
npm install next@14.2.35- Affected
- >=15.0.6 <15.0.7
- Fixed in
- 15.0.7
npm install next@15.0.7- Affected
- >=15.1.10 <15.1.11
- Fixed in
- 15.1.11
npm install next@15.1.11- Affected
- >=15.2.7 <15.2.8
- Fixed in
- 15.2.8
npm install next@15.2.8- Affected
- >=15.3.7 <15.3.8
- Fixed in
- 15.3.8
npm install next@15.3.8- Affected
- >=15.4.9 <15.4.10
- Fixed in
- 15.4.10
npm install next@15.4.10- Affected
- >=15.5.8 <15.5.9
- Fixed in
- 15.5.9
npm install next@15.5.9- Affected
- >=15.6.0-canary.59 <15.6.0-canary.60
- Fixed in
- 15.6.0-canary.60
npm install next@15.6.0-canary.60- Affected
- >=16.0.9 <16.0.10
- Fixed in
- 16.0.10
npm install next@16.0.10- Affected
- >=16.1.0-canary.17 <16.1.0-canary.19
- Fixed in
- 16.1.0-canary.19
npm install next@16.1.0-canary.19Details
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.
Is GHSA-5j59-xgg2-r9c4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected next, and gives you the command that fixes it.
References
- Linkgithub.com/vercel/next.js/security/advisories/GHSA-5j59-xgg2-r9c4
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-67779
- Packagegithub.com/vercel/next.js
- Linknextjs.org/blog/security-update-2025-12-11
- Linkreact.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components
- Linkwww.cve.org/CVERecord?id=CVE-2025-55184
- Linkwww.facebook.com/security/advisories/cve-2025-67779
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.