GHSA-5j59-xgg2-r9c4
HIGHNext has a Denial of Service with Server Components - Incomplete Fix Follow-Up
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
nextnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | next | ≥ 13.3.1-canary.0&&< 14.2.35 | 14.2.35 |
| 📦npm | next | ≥ 15.0.6&&< 15.0.7 | 15.0.7 |
| 📦npm | next | ≥ 15.1.10&&< 15.1.11 | 15.1.11 |
| 📦npm | next | ≥ 15.2.7&&< 15.2.8 | 15.2.8 |
| 📦npm | next | ≥ 15.3.7&&< 15.3.8 | 15.3.8 |
| 📦npm | next | ≥ 15.4.9&&< 15.4.10 | 15.4.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update next to 14.2.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5j59-xgg2-r9c4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-5j59-xgg2-r9c4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-5j59-xgg2-r9c4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-5j59-xgg2-r9c4 in your dependencies?
O3 detects GHSA-5j59-xgg2-r9c4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.