GHSA-h25m-26qc-wcjf
HIGHNext.js HTTP request deserialization can lead to DoS when using insecure React Server Components
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
nextnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | next | ≥ 13.0.0&&< 15.0.8 | 15.0.8 |
| 📦npm | next | ≥ 15.1.1-canary.0&&< 15.1.12 | 15.1.12 |
| 📦npm | next | ≥ 15.2.0-canary.0&&< 15.2.9 | 15.2.9 |
| 📦npm | next | ≥ 15.3.0-canary.0&&< 15.3.9 | 15.3.9 |
| 📦npm | next | ≥ 15.4.0-canary.0&&< 15.4.11 | 15.4.11 |
| 📦npm | next | ≥ 15.5.1-canary.0&&< 15.5.10 | 15.5.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 15.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h25m-26qc-wcjf 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-h25m-26qc-wcjf 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-h25m-26qc-wcjf. 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-h25m-26qc-wcjf in your dependencies?
O3 detects GHSA-h25m-26qc-wcjf across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.