GHSA-q4gf-8mx6-v5v3 Next.js has a Denial of Service with Server Components
Attackers can cause denial of service via excessive CPU usage by sending crafted requests to Next.js App Router endpoints.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-q4gf-8mx6-v5v3?
GHSA-q4gf-8mx6-v5v3 is a denial of service vulnerability in next, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
A vulnerability affects certain React Server Components packages for versions 19.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23869. You can read more about this advisory our this changelog.
A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage. This can result in denial of service in unpatched environments.
Which versions are affected by GHSA-q4gf-8mx6-v5v3?
4 open source packages ship an affected version, including next.
| Package | Affected | Fixed in |
|---|---|---|
next npm | From 13.0.0 | 15.5.15 |
next npm | From 13.0.0 | 15.5.15 |
next npm | From 16.0.0-beta.0 | 16.2.3 |
next npm | From 16.0.0-beta.0 | 16.2.3 |
How do I fix GHSA-q4gf-8mx6-v5v3?
Upgrade next to a fixed version for your release line: 15.5.15 or 16.2.3.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is GHSA-q4gf-8mx6-v5v3 being exploited?
There is no known exploitation of GHSA-q4gf-8mx6-v5v3 in the wild and no public exploit code.