React Server Components flaw CVE-2026-126187: upgrade now
CVE-2026-126187 can give remote code execution in React Server Components apps. See affected versions, how to check and fix with 19.3.1, 19.2.9, 19.1.10 or 19.0.9.
TL;DR
- CVE-2026-126187 lets an attacker run code on a server through crafted payloads sent to apps built on React Server Components, with no login.
- It affects react-server-dom-turbopack, react-server-dom-webpack and react-server-dom-parcel, from 19.0.0 up to 19.0.8, from 19.1.0 up to 19.1.9, from 19.2.0 up to 19.2.8, and 19.3.0.
- NVD records a CVSS 4.0 score of 9.5 (critical). The weakness is CWE-502.
- The advisories do not say it is exploited yet, but they recommend updating immediately.
- Upgrade to 19.3.1, 19.2.9, 19.1.10 or 19.0.9, depending on your line, then rebuild and redeploy.
What the vulnerability is
React is a JavaScript library that many sites use to build their screens. Some frameworks use a feature called React Server Components, where part of the page is rendered on the server and its result is sent to the browser as a stream. Three npm packages handle that stream for the common bundlers: react-server-dom-turbopack, react-server-dom-webpack and react-server-dom-parcel.
CVE-2026-126187 is a flaw in how those packages read incoming data. A crafted payload can lead to remote code execution on the server. The GitHub advisory GHSA-xqc2-xf4c-x3h3 classes the weakness as CWE-502, the deserialization of untrusted data, which means the server trusts the shape of data that an outsider controls.
The advisory is careful about reach. It says the problem only affects extremely rare cases, where a response carries several typed arrays together with a value the attacker controls. That narrows the risk, but a flaw that needs no account and gives code execution is still one to close quickly.
Why it matters now
NVD published the record on November 10, 2026, and the same day the React maintainers shipped fixes for four release lines. NVD lists a CVSS 4.0 score of 9.5, rated critical, and the GitHub advisory rates it critical too. The attack comes over the network, needs no privileges and no user action.
For a retailer or any team that runs a storefront on a server-rendered React framework, the server is where sessions, API keys and customer data live. Code execution there is a serious incident, not a front-end bug. The packages are also rarely listed in your own package file, because a framework pulls them in. That is why teams miss this kind of update: nobody chose the dependency, so nobody watches it.
We have no report of exploitation from the sources we cite. The maintainers still say to update immediately, and a public fix gives attackers a map of what changed. Our guide to upgrading a vulnerable npm dependency covers the general routine.
Am I affected?
You are in scope if all of these are true:
- your app has one of the three packages above, directly or through a framework;
- the version is from 19.0.0 up to 19.0.8, from 19.1.0 up to 19.1.9, from 19.2.0 up to 19.2.8, or 19.3.0;
- your app uses tooling that handles React Server Components, and its React code uses a server.
The advisory states that apps where the React code never runs on a server, and apps with no framework, bundler or plugin that handles React Server Components, are not affected. Still, confirm it rather than assume it.
To check one project by hand, run these in the project folder:
npm ls react-server-dom-webpack
npm ls react-server-dom-parcel
npm ls react-server-dom-turbopackEach command prints every copy of the package in the dependency tree and the version. Read the production build too: a lockfile in a repository shows what you intend to ship, and the image or server shows what is actually running. If a package is not found, the command says so.
How to fix CVE-2026-126187
The fix was back ported to each affected line, so you do not have to change major version. Follow these steps:
- Find every project that uses one of the three packages, including ones pulled in by a framework, and note which of the four release lines each one is on.
- Upgrade to the fixed version for that line: 19.3.1, 19.2.9, 19.1.10 or 19.0.9. If your framework pins these packages, upgrade the framework to a release that uses a fixed version, or add an override in your package manager and test it.
- Reinstall from a clean state and commit the updated lockfile, so the build does not resolve an older copy.
- Run your tests, rebuild the application and redeploy every environment, including preview and staging copies that are reachable from the internet.
- Run
npm lsagain for each package and confirm the installed version is a fixed one.
If you cannot upgrade today, limit exposure while you plan it: put the app behind your web application firewall rules, and reduce who can reach the server-rendered endpoints. This is a stopgap, not a fix. The vendor advisory linked below is the place to read about any further guidance.
How to check with Stackurity
Checking one project is easy. Checking all of them is the hard part. Stackurity keeps one live inventory of the libraries in your repositories and the libraries your deployed applications actually load, and matches it against new advisories every hour. A transitive dependency that nobody listed shows up the same way a direct one does.
When the advisory lands, the finding names the version to move to and why it applies. After you upgrade, Check again asks for a fresh report and records whether the issue is gone. You can also stop a vulnerable change before it ships with the CI gate. The remediation documentation explains how fixes are grouped and verified. Start a free trial of Stackurity and see where these packages run.
FAQ
Does CVE-2026-126187 affect every React app?
No. The advisory says an app where the React code never runs on a server is not affected, and neither is an app with no framework, bundler or plugin that handles React Server Components. It also describes the flaw as limited to extremely rare cases, where a response carries several typed arrays together with a value the attacker controls. Check your lockfile anyway, because the vulnerable packages can arrive as dependencies of a framework.
Which versions are fixed?
The fixed versions are 19.3.1, 19.2.9, 19.1.10 and 19.0.9 for react-server-dom-turbopack, react-server-dom-webpack and react-server-dom-parcel. Use the fix that matches the line you are on, and move to a newer line only if your framework supports it.
Is CVE-2026-126187 being exploited?
The advisories we cite do not say it is. They do recommend updating immediately, and the flaw needs no login, so treat it as urgent for any internet-facing app that uses React Server Components.
How serious is it?
NVD records a CVSS 4.0 score of 9.5, rated critical, and the GitHub advisory also rates it critical. The weakness is CWE-502, the deserialization of untrusted data.
Does Stackurity find vulnerable React packages?
Stackurity reads npm lockfiles in repositories and the libraries that deployed applications load, then matches them against advisories every hour. After you upgrade, Check again records whether the issue is gone.
Sources
Sources: NVD: CVE-2026-126187, GitHub Advisory Database: GHSA-xqc2-xf4c-x3h3 and the Stackurity product facts.