Summary
References
See the blog post for more information and upgrade instructions.
Impact
There is a denial of service vulnerability in React Server Components.
React recommends updating immediately.
The vulnerability exists in versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1 of:
These issues are present in the patches published last week.
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
CVE-2025-55184 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (19.0.2, 19.1.3, 19.2.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Fixes were back ported to versions 19.0.2, 19.1.3, and 19.2.2.
If you are using any of the above packages please upgrade to any of the fixed versions immediately.
If your app’s React code does not use a server, your app is not affected by this vulnerability. If your app does not use a framework, bundler, or bundler plugin that supports React Server Components, your app is not affected by this vulnerability.
Frequently Asked Questions
- What is CVE-2025-55184? CVE-2025-55184 is a high-severity uncontrolled resource consumption vulnerability in react-server-dom-parcel (npm), affecting versions >= 19.0.0, < 19.0.2. It is fixed in 19.0.2, 19.1.3, 19.2.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- How severe is CVE-2025-55184? CVE-2025-55184 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2025-55184?
react-server-dom-parcel(npm) (versions >= 19.0.0, < 19.0.2)react-server-dom-turbopack(npm) (versions >= 19.0.0, < 19.0.2)react-server-dom-webpack(npm) (versions >= 19.0.0, < 19.0.2)
- Is there a fix for CVE-2025-55184? Yes. CVE-2025-55184 is fixed in 19.0.2, 19.1.3, 19.2.2. Upgrade to this version or later.
- Is CVE-2025-55184 exploitable, and should I be worried? Whether CVE-2025-55184 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-55184 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-55184?
- Upgrade
react-server-dom-parcelto 19.0.2 or later - Upgrade
react-server-dom-turbopackto 19.0.2 or later - Upgrade
react-server-dom-webpackto 19.0.2 or later - Upgrade
react-server-dom-parcelto 19.1.3 or later - Upgrade
react-server-dom-parcelto 19.2.2 or later - Upgrade
react-server-dom-turbopackto 19.1.3 or later - Upgrade
react-server-dom-turbopackto 19.2.2 or later - Upgrade
react-server-dom-webpackto 19.1.3 or later - Upgrade
react-server-dom-webpackto 19.2.2 or later
- Upgrade