# GHSA-5j59-xgg2-r9c4: Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up > Attackers can cause denial of service in Next.js apps by sending crafted requests to Server Function endpoints, triggering infinite loops in React Server Components. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Dec 2025 ## What is GHSA-5j59-xgg2-r9c4? GHSA-5j59-xgg2-r9c4 is a denial of service vulnerability in next, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description It was discovered that the fix for [CVE-2025-55184](https://github.com/advisories/GHSA-2m3v-v2m8-q956) 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](https://www.cve.org/CVERecord?id=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. ## Which versions are affected by GHSA-5j59-xgg2-r9c4? 20 open source packages ship an affected version, including next. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `next` | npm | From 13.3.1-canary.0 | 14.2.35 | | `next` | npm | From 13.3.1-canary.0 | 14.2.35 | | `next` | npm | From 15.0.6 | 15.0.7 | | `next` | npm | From 15.0.6 | 15.0.7 | | `next` | npm | From 15.1.10 | 15.1.11 | | `next` | npm | From 15.1.10 | 15.1.11 | | `next` | npm | From 15.2.7 | 15.2.8 | | `next` | npm | From 15.2.7 | 15.2.8 | | `next` | npm | From 15.3.7 | 15.3.8 | | `next` | npm | From 15.3.7 | 15.3.8 | | `next` | npm | From 15.4.9 | 15.4.10 | | `next` | npm | From 15.4.9 | 15.4.10 | | `next` | npm | From 15.5.8 | 15.5.9 | | `next` | npm | From 15.5.8 | 15.5.9 | | `next` | npm | From 15.6.0-canary.59 | 15.6.0-canary.60 | | `next` | npm | From 15.6.0-canary.59 | 15.6.0-canary.60 | | `next` | npm | From 16.0.9 | 16.0.10 | | `next` | npm | From 16.0.9 | 16.0.10 | | `next` | npm | From 16.1.0-canary.17 | 16.1.0-canary.19 | | `next` | npm | From 16.1.0-canary.17 | 16.1.0-canary.19 | ## How do I fix GHSA-5j59-xgg2-r9c4? Upgrade next to a fixed version for your release line: 14.2.35, 15.0.7, 15.1.11 or 15.2.8. ## Is GHSA-5j59-xgg2-r9c4 being exploited? There is no known exploitation of GHSA-5j59-xgg2-r9c4 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-5j59-xgg2-r9c4 and fix it if it is affected. What it is: GHSA-5j59-xgg2-r9c4 is a denial of service vulnerability in next, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of GHSA-5j59-xgg2-r9c4 in the wild and no public exploit code. Affected packages and fixed versions: - next (npm): affected from 13.3.1-canary.0; fixed in 14.2.35 - next (npm): affected from 13.3.1-canary.0; fixed in 14.2.35 - next (npm): affected from 15.0.6; fixed in 15.0.7 - next (npm): affected from 15.0.6; fixed in 15.0.7 - next (npm): affected from 15.1.10; fixed in 15.1.11 - next (npm): affected from 15.1.10; fixed in 15.1.11 - next (npm): affected from 15.2.7; fixed in 15.2.8 - next (npm): affected from 15.2.7; fixed in 15.2.8 - next (npm): affected from 15.3.7; fixed in 15.3.8 - next (npm): affected from 15.3.7; fixed in 15.3.8 - next (npm): affected from 15.4.9; fixed in 15.4.10 - next (npm): affected from 15.4.9; fixed in 15.4.10 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-5j59-xgg2-r9c4/ (Markdown: https://insights.sbomify.com/GHSA-5j59-xgg2-r9c4/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-5j59-xgg2-r9c4 --- From sbomify Insights: https://insights.sbomify.com/GHSA-5j59-xgg2-r9c4/ Summaries are generated and may contain mistakes; the official description above is the record.