A server rack mailroom accepting a tampered parcel while a patched gate blocks a second one

On 3 December 2025, the React team disclosed a critical security flaw in React Server Components, tracked as CVE-2025-55182 and nicknamed React2Shell. It carries the highest possible severity score, 10.0, and is also tracked in Next.js as CVE-2025-66478. China-linked groups began exploiting it quickly, and the US cybersecurity agency CISA added it to its list of actively exploited flaws on 5 December.

What is going on

React Server Components let a site build parts of a page on the server instead of in the visitor's browser. To do that, the server unpacks data that arrives with a request. That unpacking step, called deserialization, is where the flaw sits.

Think of a mailroom that opens every parcel and follows whatever instructions it finds inside, without checking who sent it. An attacker can send a crafted request and have the server run their commands. No password, no account and no user interaction are needed, which is why it is called unauthenticated remote code execution, or RCE.

Diagram showing a crafted request reaching a React server and being blocked after patching
The crafted request is unpacked and executed on vulnerable versions, and rejected once React and Next.js are patched.

Who is affected

The flaw affects Next.js apps using the App Router on versions 15.x, 16.x and 14.3 canary. It also affects React Router, Waku, Parcel and Vite RSC apps running React 19.0 through 19.2.0.

If your site was built in the last couple of years by an agency using modern JavaScript tooling, it is worth asking which framework it uses. Classic WordPress, Shopify or static HTML sites are not affected by this particular issue.

What to do now

  1. Ask your developer or hosting provider whether your site runs Next.js or another React Server Components framework, and on which version.
  2. Upgrade React to 19.0.1, 19.1.2 or 19.2.1 and later.
  3. Upgrade Next.js to a patched release such as 15.5.7 or 16.0.7.
  4. Rotate all application secrets afterwards: API keys, database passwords, tokens and signing keys. Assume anything stored on the server could have been read.
  5. Keep the upgrade in place for staging and preview environments too, not only the live site.

How to check your own site

The free Website Security Check looks for outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps, so it is a quick way to see the state of your site in general. For React2Shell specifically, the version number of your framework is what matters, so confirm it with whoever maintains the code. If you want deeper coverage of your own site, you can run a full scan, which adds active OWASP Top 10 testing and port and service checks with CVE matching, but only against sites whose ownership you have verified.

Source: React blog, critical security vulnerability in React Server Components, December 2025.