GHSA-h25m-26qc-wcjf Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
Attackers can cause denial of service in Next.js applications by sending crafted HTTP requests to Server Function endpoints, leading to resource exhaustion.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-h25m-26qc-wcjf?
GHSA-h25m-26qc-wcjf is a denial of service vulnerability in next, published on 28 Jan 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.0.x, 19.1.x, and 19.2.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-23864.
A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage, out-of-memory exceptions, or server crashes. This can result in denial of service in unpatched environments.
Which versions are affected by GHSA-h25m-26qc-wcjf?
18 open source packages ship an affected version, including next.
| Package | Affected | Fixed in |
|---|---|---|
next npm | From 13.0.0 | 15.0.8 |
next npm | From 13.0.0 | 15.0.8 |
next npm | From 15.1.1-canary.0 | 15.1.12 |
next npm | From 15.1.1-canary.0 | 15.1.12 |
next npm | From 15.2.0-canary.0 | 15.2.9 |
next npm | From 15.2.0-canary.0 | 15.2.9 |
12 more packages
next npm | From 15.3.0-canary.0 | 15.3.9 |
next npm | From 15.3.0-canary.0 | 15.3.9 |
next npm | From 15.4.0-canary.0 | 15.4.11 |
next npm | From 15.4.0-canary.0 | 15.4.11 |
next npm | From 15.5.1-canary.0 | 15.5.10 |
next npm | From 15.5.1-canary.0 | 15.5.10 |
next npm | From 15.6.0-canary.0 | 15.6.0-canary.61 |
next npm | From 15.6.0-canary.0 | 15.6.0-canary.61 |
next npm | From 16.0.0-beta.0 | 16.0.11 |
next npm | From 16.0.0-beta.0 | 16.0.11 |
next npm | From 16.1.0-canary.0 | 16.1.5 |
next npm | From 16.1.0-canary.0 | 16.1.5 |
How do I fix GHSA-h25m-26qc-wcjf?
Upgrade next to a fixed version for your release line: 15.0.8, 15.1.12, 15.2.9 or 15.3.9.
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-h25m-26qc-wcjf being exploited?
There is no known exploitation of GHSA-h25m-26qc-wcjf in the wild and no public exploit code.