# GHSA-mwv6-3258-q52c: Next Vulnerable to Denial of Service with Server Components > Attackers can cause server hangs and CPU exhaustion via malicious HTTP requests to App Router endpoints, leading to denial of service. - **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:** 11 Dec 2025 ## What is GHSA-mwv6-3258-q52c? GHSA-mwv6-3258-q52c is a denial of service vulnerability in next, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as [CVE-2025-55184](https://www.cve.org/CVERecord?id=CVE-2025-55184). A malicious HTTP request can be crafted and sent to any App Router endpoint that, when deserialized, can cause the server process to hang and consume CPU. This can result in denial of service in unpatched environments. ## Which versions are affected by GHSA-mwv6-3258-q52c? 20 open source packages ship an affected version, including next. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `next` | npm | From 13.3.0 | 14.2.34 | | `next` | npm | From 13.3.0 | 14.2.34 | | `next` | npm | From 15.0.0-canary.0 | 15.0.6 | | `next` | npm | From 15.0.0-canary.0 | 15.0.6 | | `next` | npm | From 15.1.1-canary.0 | 15.1.10 | | `next` | npm | From 15.1.1-canary.0 | 15.1.10 | | `next` | npm | From 15.2.0-canary.0 | 15.2.7 | | `next` | npm | From 15.2.0-canary.0 | 15.2.7 | | `next` | npm | From 15.3.0-canary.0 | 15.3.7 | | `next` | npm | From 15.3.0-canary.0 | 15.3.7 | | `next` | npm | From 15.4.0-canary.0 | 15.4.9 | | `next` | npm | From 15.4.0-canary.0 | 15.4.9 | | `next` | npm | From 15.5.1-canary.0 | 15.5.8 | | `next` | npm | From 15.5.1-canary.0 | 15.5.8 | | `next` | npm | From 15.6.0-canary.0 | 15.6.0-canary.59 | | `next` | npm | From 15.6.0-canary.0 | 15.6.0-canary.59 | | `next` | npm | From 16.0.0-beta.0 | 16.0.9 | | `next` | npm | From 16.0.0-beta.0 | 16.0.9 | | `next` | npm | From 16.1.0-canary.0 | 16.1.0-canary.17 | | `next` | npm | From 16.1.0-canary.0 | 16.1.0-canary.17 | ## How do I fix GHSA-mwv6-3258-q52c? Upgrade next to a fixed version for your release line: 14.2.34, 15.0.6, 15.1.10 or 15.2.7. ## Is GHSA-mwv6-3258-q52c being exploited? There is no known exploitation of GHSA-mwv6-3258-q52c in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-mwv6-3258-q52c and fix it if it is affected. What it is: GHSA-mwv6-3258-q52c is a denial of service vulnerability in next, published on 11 Dec 2025. 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-mwv6-3258-q52c in the wild and no public exploit code. Affected packages and fixed versions: - next (npm): affected from 13.3.0; fixed in 14.2.34 - next (npm): affected from 13.3.0; fixed in 14.2.34 - next (npm): affected from 15.0.0-canary.0; fixed in 15.0.6 - next (npm): affected from 15.0.0-canary.0; fixed in 15.0.6 - next (npm): affected from 15.1.1-canary.0; fixed in 15.1.10 - next (npm): affected from 15.1.1-canary.0; fixed in 15.1.10 - next (npm): affected from 15.2.0-canary.0; fixed in 15.2.7 - next (npm): affected from 15.2.0-canary.0; fixed in 15.2.7 - next (npm): affected from 15.3.0-canary.0; fixed in 15.3.7 - next (npm): affected from 15.3.0-canary.0; fixed in 15.3.7 - next (npm): affected from 15.4.0-canary.0; fixed in 15.4.9 - next (npm): affected from 15.4.0-canary.0; fixed in 15.4.9 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-mwv6-3258-q52c/ (Markdown: https://insights.sbomify.com/GHSA-mwv6-3258-q52c/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-mwv6-3258-q52c --- From sbomify Insights: https://insights.sbomify.com/GHSA-mwv6-3258-q52c/ Summaries are generated and may contain mistakes; the official description above is the record.