Act nowVulnerabilities

React Server Components has a new critical flaw that lets an unauthenticated attacker run code: update react-server-dom-* to 19.0.9, 19.1.10, 19.2.9 or 19.3.1

The React team published a critical advisory (GHSA-xqc2-xf4c-x3h3, CVSS 4.0 score 9.5) for unauthenticated remote code execution in the react-server-dom-webpack, parcel and turbopack packages. It only applies in rare cases, but the advice is to update immediately. What we verified and how to check your app.

How urgent

Act now

Who is affected

Apps that use React Server Components through a framework, bundler or plugin that supports them, with react-server-dom-webpack, react-server-dom-parcel or react-server-dom-turbopack in versions 19.0.0 to 19.0.8, 19.1.0 to 19.1.9, 19.2.0 to 19.2.8 or 19.3.0. Apps without a server-side React part, or without a framework that supports Server Components, are not affected, according to the advisory

What to do

Find out which version of the three react-server-dom packages your app really installs (check the lockfile, not only package.json), and update to 19.0.9, 19.1.10, 19.2.9 or 19.3.1 or later, usually through your framework's own update, then redeploy

Published 10 Nov 2026 · Sources last checked 10 Nov 2026No. 67 / 87

What happened

The React team published a security advisory called "Unauthenticated Remote Code ExecutionRCE (remote code execution) A flaw that lets an attacker run their own code on your server or device from a distance. Tap again to open the glossary in React Server Components", identifier GHSA-xqc2-xf4c-x3h3, rated Critical: 9.5 out of 10 on the CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary 4.0 scale. The vector is over the network, with low complexity, no privileges and no user interaction.

The advisory says that crafted payloads aimed at frameworks that support React Server Components can lead to remote code execution. It also says this "only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value", and still recommends updating immediately. It has no CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary ID yet. The credit goes to a finder who goes by "evolutionstorm". We did not see a publication date on the page we read; social posts about it appeared on 9 November.

It is a separate advisory from earlier ones: the same list shows older React Server Components advisories for remote code execution, source code exposure and denial of service.

Who is affected

The advisory lists three npm packages, react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack, in versions 19.0.0 to 19.0.8, 19.1.0 to 19.1.9, 19.2.0 to 19.2.8 and 19.3.0.

  • Apps built with a framework or bundler that supports React Server Components. Those packages usually arrive as a dependency of the framework, not something you installed yourself. The advisory does not name the frameworks, so we cannot tell you which ones ship these packages.
  • Not affected, according to the advisory: apps whose React code does not use a server, and apps that do not use a framework, bundler or plugin that supports Server Components.
  • Hosting providers and other frameworks: they may publish their own notices. We did not look for them.

What to do

  1. Find out if you use these packages and at which version. Look in the lockfile of your project, because they are often installed indirectly. Search for the three package names.
  2. Update to a fixed version: the advisory says fixes were backported to 19.0.9, 19.1.10, 19.2.9 and 19.3.1. If you are on another line, move to the latest release of it.
  3. Do it through your framework when you can: its update usually brings the right version of these packages. Check that the lockfile really changed.
  4. Redeploy. The fix does nothing until the new build is live. This is our advice.
  5. If you cannot update today, ask your framework or host what they recommend. The advisory gives no workaround and we have not seen one.
  6. If you run a team, put this in the same place as other critical updates and note who confirmed which app.

What we could not confirm

We read the advisory and the list of the repository's advisories directly. We do not know of exploitation in the wild: the advisory does not say. We could not tell which frameworks, hosts or versions of them are affected, how rare the "extremely rare cases" really are in typical apps, or when exactly the advisory went public. It has no CVE ID, so tools that match on CVE may not flag it yet.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks