# 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. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Jan 2026 ## 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](https://github.com/facebook/react/security/advisories/GHSA-83fc-fqcc-2hmg). 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 | Ecosystem | 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 | | `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. ## 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. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-h25m-26qc-wcjf and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of GHSA-h25m-26qc-wcjf in the wild and no public exploit code. Affected packages and fixed versions: - next (npm): affected from 13.0.0; fixed in 15.0.8 - next (npm): affected from 13.0.0; fixed in 15.0.8 - next (npm): affected from 15.1.1-canary.0; fixed in 15.1.12 - next (npm): affected from 15.1.1-canary.0; fixed in 15.1.12 - next (npm): affected from 15.2.0-canary.0; fixed in 15.2.9 - next (npm): affected from 15.2.0-canary.0; fixed in 15.2.9 - next (npm): affected from 15.3.0-canary.0; fixed in 15.3.9 - next (npm): affected from 15.3.0-canary.0; fixed in 15.3.9 - next (npm): affected from 15.4.0-canary.0; fixed in 15.4.11 - next (npm): affected from 15.4.0-canary.0; fixed in 15.4.11 - next (npm): affected from 15.5.1-canary.0; fixed in 15.5.10 - next (npm): affected from 15.5.1-canary.0; fixed in 15.5.10 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-h25m-26qc-wcjf/ (Markdown: https://insights.sbomify.com/GHSA-h25m-26qc-wcjf/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-h25m-26qc-wcjf --- From sbomify Insights: https://insights.sbomify.com/GHSA-h25m-26qc-wcjf/ Summaries are generated and may contain mistakes; the official description above is the record.