GHSA-h25m-26qc-wcjf — next
HIGHGHSA-h25m-26qc-wcjf is a high-severity (CVSS 7.5) remote code execution vulnerability in next. A fix is available for next — see the affected versions and patch details below.
Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
Real-World Exposure
next📦next📦next📦next📦next📦next📦next📦next+1 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | next | ≥ 13.0.0&&< 15.0.8 | 15.0.8npm install next@15.0.8 |
| 📦npm | next | ≥ 15.1.1-canary.0&&< 15.1.12 | 15.1.12npm install next@15.1.12 |
| 📦npm | next | ≥ 15.2.0-canary.0&&< 15.2.9 | 15.2.9npm install next@15.2.9 |
| 📦npm | next | ≥ 15.3.0-canary.0&&< 15.3.9 | 15.3.9npm install next@15.3.9 |
| 📦npm | next | ≥ 15.4.0-canary.0&&< 15.4.11 | 15.4.11npm install next@15.4.11 |
| 📦npm | next | ≥ 15.5.1-canary.0&&< 15.5.10 | 15.5.10npm install next@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h25m-26qc-wcjf can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-h25m-26qc-wcjf across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.