CVE-2025-55182

References

See the blog post for more information and upgrade instructions.

There is an unauthenticated remote code execution vulnerability in React Server Components.

We recommend upgrading immediately.

The vulnerability is present in versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 of:

• react-server-dom-webpack
• react-server-dom-parcel
• react-server-dom-turbopack

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2025-55182 has a CVSS score of 10.0 (Critical). 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.1.2, 19.2.1, 19.0.1); upgrading removes the vulnerable code path.

Kodem intelligence

A fix was introduced in versions 19.0.1, 19.1.2, and 19.2.1. 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.

1. What is CVE-2025-55182? CVE-2025-55182 is a critical-severity insecure deserialization vulnerability in react-server-dom-webpack (npm), affecting versions >= 19.1.0, < 19.1.2. It is fixed in 19.1.2, 19.2.1, 19.0.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2025-55182? CVE-2025-55182 has a CVSS score of 10.0 (Critical). 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.
3. Which packages are affected by CVE-2025-55182?
   • react-server-dom-webpack (npm) (versions >= 19.1.0, < 19.1.2)
   • react-server-dom-turbopack (npm) (versions >= 19.1.0, < 19.1.2)
   • react-server-dom-parcel (npm) (versions >= 19.1.0, < 19.1.2)
4. Is there a fix for CVE-2025-55182? Yes. CVE-2025-55182 is fixed in 19.1.2, 19.2.1, 19.0.1. Upgrade to this version or later.
5. Is CVE-2025-55182 exploitable, and should I be worried? Whether CVE-2025-55182 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
6. What actually determines whether CVE-2025-55182 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.
7. How do I fix CVE-2025-55182?
   • Upgrade react-server-dom-webpack to 19.1.2 or later
   • Upgrade react-server-dom-webpack to 19.2.1 or later
   • Upgrade react-server-dom-turbopack to 19.1.2 or later
   • Upgrade react-server-dom-turbopack to 19.2.1 or later
   • Upgrade react-server-dom-parcel to 19.1.2 or later
   • Upgrade react-server-dom-parcel to 19.2.1 or later
   • Upgrade react-server-dom-turbopack to 19.0.1 or later
   • Upgrade react-server-dom-parcel to 19.0.1 or later
   • Upgrade react-server-dom-webpack to 19.0.1 or later