GHSA-5j59-xgg2-r9c4: 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.
Published Dec 12, 2025 · Updated Jan 15, 2026
Affected packages
next
- Ecosystem
- npm
- Affected
- >= 13.3.1-canary.0, < 14.2.35
- Fixed in
- 14.2.35
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.0.6, < 15.0.7
- Fixed in
- 15.0.7
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.1.10, < 15.1.11
- Fixed in
- 15.1.11
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.2.7, < 15.2.8
- Fixed in
- 15.2.8
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.3.7, < 15.3.8
- Fixed in
- 15.3.8
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.4.9, < 15.4.10
- Fixed in
- 15.4.10
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.5.8, < 15.5.9
- Fixed in
- 15.5.9
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 15.6.0-canary.59, < 15.6.0-canary.60
- Fixed in
- 15.6.0-canary.60
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 16.0.9, < 16.0.10
- Fixed in
- 16.0.10
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 16.1.0-canary.17, < 16.1.0-canary.19
- Fixed in
- 16.1.0-canary.19
- Check
npm ls next
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to xpertforextradeinc.
References
- https://github.com/vercel/next.js/security/advisories/GHSA-5j59-xgg2-r9c4
- https://nvd.nist.gov/vuln/detail/CVE-2025-67779
- https://nextjs.org/blog/security-update-2025-12-11
- https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components
- https://www.cve.org/CVERecord?id=CVE-2025-55184
- https://www.facebook.com/security/advisories/cve-2025-67779
- https://github.com/advisories/GHSA-5j59-xgg2-r9c4
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-119346
Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
medium6.0Nov 19, 2026CVE-2026-119347
Next.js: SVG rejection bypass in the image optimization
medium6.9Nov 19, 2026CVE-2026-119348
Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
medium6.3Nov 19, 2026CVE-2026-119349
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
medium6.3Nov 19, 2026CVE-2026-119350
Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
medium6.3Nov 19, 2026CVE-2026-119351
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
medium6.3Nov 17, 2026
