# CVE-2025-55184: Denial of Service Vulnerability in React Server Components > Attackers can cause a denial of service by sending malicious payloads to React Server Function endpoints, hanging the server process. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **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 - **Updated:** 15 Dec 2025 - **Also known as:** GHSA-2m3v-v2m8-q956 ## What is CVE-2025-55184? CVE-2025-55184 is a high-severity denial of service vulnerability in Vercel Next.js, 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 pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1, including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints, which can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2025-55184? 18 open source packages ship an affected version, including react-server-dom-parcel, react-server-dom-turbopack and react-server-dom-webpack. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `react-server-dom-parcel` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-parcel` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-parcel` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-parcel` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-parcel` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-parcel` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-turbopack` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-turbopack` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-turbopack` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-turbopack` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-turbopack` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-turbopack` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-webpack` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-webpack` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-webpack` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-webpack` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-webpack` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-webpack` | npm | From 19.2.0 | 19.2.2 | Products: Facebook React, Vercel Next.js. ## How do I fix CVE-2025-55184? Upgrade react-server-dom-parcel to a fixed version for your release line: 19.0.2, 19.1.3 or 19.2.2. ## Is CVE-2025-55184 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55184 exists. Public exploit code: - https://github.com/cybertechajju/CVE-2025-55184-POC-Expolit (github_poc): https://github.com/cybertechajju/CVE-2025-55184-POC-Expolit - https://github.com/ejpir/CVE-2025-55184 (github_poc): https://github.com/ejpir/CVE-2025-55184 - https://github.com/hans362/CVE-2025-55184-poc (github_poc): https://github.com/hans362/CVE-2025-55184-poc - Python script for Testing CVE-2025-55184 (github_poc): https://github.com/KkHackingLearning/CVE-2025-55184_Testing - https://github.com/KingHacker353/CVE-2025-55184 (github_poc): https://github.com/KingHacker353/CVE-2025-55184 - OpsGuard eliminates the "3 AM PagerDuty" nightmare, specifically protecting against threats like the recent CVE-2025-55184 (Next.js DoS) (github_poc): https://github.com/shubham-01-star/OpsGuard-simulation ## Other vulnerabilities in Vercel Next.js - [CVE-2025-55182](https://insights.sbomify.com/CVE-2025-55182/): Meta React Server Components Remote Code Execution (critical 10.0, exploited in the wild) - [CVE-2026-23864](https://insights.sbomify.com/CVE-2026-23864/): React Server Components have multiple Denial of Service Vulnerabilities (high 7.5) - [CVE-2025-67779](https://insights.sbomify.com/CVE-2025-67779/): Denial of Service Vulnerability in React Server Components (high 7.5) - [CVE-2018-6341](https://insights.sbomify.com/CVE-2018-6341/): Cross-Site Scripting in react-dom (medium 6.1) - [CVE-2025-55183](https://insights.sbomify.com/CVE-2025-55183/): Source Code Exposure Vulnerability in React Server Components (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-55184 and fix it if it is affected. What it is: CVE-2025-55184 is a high-severity denial of service vulnerability in Vercel Next.js, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55184 exists. Affected packages and fixed versions: - react-server-dom-parcel (npm): affected from 19.0.0; fixed in 19.0.2 - react-server-dom-parcel (npm): affected from 19.0.0; fixed in 19.0.2 - react-server-dom-parcel (npm): affected from 19.1.0; fixed in 19.1.3 - react-server-dom-parcel (npm): affected from 19.1.0; fixed in 19.1.3 - react-server-dom-parcel (npm): affected from 19.2.0; fixed in 19.2.2 - react-server-dom-parcel (npm): affected from 19.2.0; fixed in 19.2.2 - react-server-dom-turbopack (npm): affected from 19.0.0; fixed in 19.0.2 - react-server-dom-turbopack (npm): affected from 19.0.0; fixed in 19.0.2 - react-server-dom-turbopack (npm): affected from 19.1.0; fixed in 19.1.3 - react-server-dom-turbopack (npm): affected from 19.1.0; fixed in 19.1.3 - react-server-dom-turbopack (npm): affected from 19.2.0; fixed in 19.2.2 - react-server-dom-turbopack (npm): affected from 19.2.0; fixed in 19.2.2 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/CVE-2025-55184/ (Markdown: https://insights.sbomify.com/CVE-2025-55184/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55184 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55184 - OSV: https://osv.dev/vulnerability/CVE-2025-55184 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-55184/ Summaries are generated and may contain mistakes; the official description above is the record.