BSI warns of massively exploited React2Shell flaw CVE-2025-55182 in React Server Components

Germany’s Federal Office for Information Security (BSI) has issued a cybersecurity warning about CVE-2025-55182, nicknamed React2Shell. The flaw is a CVSS 10.0 remote code execution vulnerability in React Server Components that also affects Next.js and other frameworks built on them. The React team disclosed it on 3 December 2025, and the BSI warning followed on 4 December.

What happened

The vulnerability lets an unauthenticated attacker run code on a server that uses vulnerable React Server Components packages. Shortly after disclosure, AWS reported several threat actors attempting to exploit it, and Baden-Württemberg’s cybersecurity agency (CSBW) noted activity attributed to China-linked actors. In its advisory the BSI rates the threat as massive active exploitation and warns that exposed, unpatched web applications could be compromised within a very short time. It also advises operators to treat applications that were not patched promptly as potentially compromised.

The BSI cited Wiz figures showing how common the affected stack is: about 70% of cloud environments contain Next.js, 44% expose it publicly, and an estimated 39% of environments were vulnerable.

Technical details

  • Affected packages: react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack in versions 19.0, 19.1.0, 19.1.1 and 19.2.0
  • Fixed versions: 19.0.1, 19.1.2 and 19.2.1
  • Downstream frameworks: next, react-router, waku, @parcel/rsc, @vitejs/plugin-rsc and rwsdk
  • The Next.js-specific identifier CVE-2025-66478 was rejected as a duplicate and folded into CVE-2025-55182.

Who is affected

The flaw affects any organisation running React 19 server-side rendering with Server Components, including many Next.js 15 and 16 deployments. Purely client-side React applications are not exposed.

Recommendations

  • Upgrade the React Server Components packages to 19.0.1, 19.1.2 or 19.2.1 and update Next.js and other frameworks to their patched releases. Then rebuild and redeploy.
  • If patching was delayed, check servers for signs of compromise. Look for unexpected child processes of the Node.js runtime, new files in application directories and outbound connections to unknown hosts.
  • Rotate environment secrets, such as database credentials and API keys, on any instance that was internet-facing and unpatched.
  • Put a WAF rule in front of exposed applications as a temporary measure, but do not rely on it in place of patching.
  • Follow the updated BSI advisory, which is being revised as further related flaws are analysed.

Sources