On this page (7 sections)
A critical vulnerability, tracked as CVE-2026-126187, affects three npm packages that implement React Server Components: react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack. According to the GitHub advisory, specially crafted payloads sent to a framework that supports React Server Components can lead to remote code execution, and no authentication is required.
If you build or host server-rendered React applications (for example through a framework or bundler plugin that supports Server Components), you should check your dependency tree today. Fixed versions have been released. The advisory also describes the issue as limited to rare cases, which is covered below.
What happened
The React project published an advisory titled "Unauthenticated Remote Code Execution in React Server Components" on Oct 14, 2026. The GitHub Advisory Database reviewed it and updated its record on Nov 10, 2026. The advisory says fixes were backported to four release lines, so teams on older 19.x minors have a patch available without jumping to a newer line.
Only one independent publisher covers this story so far, and that is the advisory itself. There is no separate confirmation of exploitation in the wild, and the research does not include a CWE classification or technical root-cause write-up beyond what is summarized here. Treat details beyond the advisory as unconfirmed.
Technical details
React Server Components let a server send component data to the browser, and the client-side packages decode that data. The three affected packages are the integration layers for different bundlers: webpack, Parcel and Turbopack. The advisory states that crafted payloads aimed at frameworks supporting this feature can result in remote code execution on the server.
The advisory adds an important qualifier: it "only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value." That narrows the conditions, but the maintainers still recommend updating immediately, and the CVSS v4 metrics rate the attack as network-reachable, low complexity, requiring no privileges and no user interaction, with high impact on confidentiality, integrity and availability of the vulnerable system.
We are deliberately not describing how a payload would be built. The advisory does not publish exploit details in the text available to us, and defenders do not need them to patch.
Who is affected
You are potentially exposed if your project depends, directly or through a framework, on any of the three packages in a vulnerable version range. The advisory gives two clear exclusions:
- If your app's React code does not use a server, it is not affected.
- If your app does not use a framework, bundler or bundler plugin that supports React Server Components, it is not affected.
Many teams never install these packages by name. They arrive as transitive dependencies of a framework, so a check of your lockfile matters more than a check of package.json.
| Release line | Vulnerable | Fixed |
|---|---|---|
| 19.0.x | >= 19.0.0, < 19.0.9 | 19.0.9 |
| 19.1.x | >= 19.1.0, < 19.1.10 | 19.1.10 |
| 19.2.x | >= 19.2.0, < 19.2.9 | 19.2.9 |
| 19.3.x | >= 19.3.0, < 19.3.1 | 19.3.1 |
How to check your exposure
Run these read-only commands from the root of each project (and each deployed build directory that contains a lockfile). They list every installed copy of the affected packages, including nested ones, and print versions. Compare the output with the table above.
npm ls react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopackIf you use Yarn or pnpm, use the equivalent query for your package manager. Each prints the dependency path, which tells you which framework pulled the package in.
pnpm why react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopackyarn list --pattern react-server-domAn empty result means the packages are not installed in that project. A version inside a vulnerable range means you should update. Also check CI images, container images and any server where a built app is deployed, since a stale build can keep an old version running.
What to do now
- Inventory every app that uses a framework or bundler plugin with React Server Components support.
- Run the version checks above and note any copy of the three packages in a vulnerable range.
- Upgrade to the fixed version for your release line: 19.0.9, 19.1.10, 19.2.9 or 19.3.1. Prefer updating your framework to a release that depends on these versions if that is how the package is installed.
- Regenerate your lockfile so transitive copies are updated, then confirm with the version check again.
- Rebuild and redeploy, including container images, then restart the running service so the old code is not still loaded.
- Review recent server logs for unusual requests to your Server Components endpoints and for unexpected processes or outbound connections from the app host.
- If you suspect compromise before patching, rotate secrets available to the server (API keys, database credentials, tokens) and follow an incident process.
If you cannot patch immediately, the advisory offers no workaround in the text we have. Limiting exposure of the affected endpoints is a reasonable stopgap, but it is not a substitute for updating. A web application firewall can add a layer of filtering, though no vendor has stated that any specific rule covers this flaw.
Detection and monitoring afterwards
Remote code execution on an application server usually shows up as side effects rather than as the initial request. After patching, keep watching for:
- Unexpected child processes or shell activity from the Node.js process.
- New or modified files in the application directory, or new scheduled jobs.
- Outbound connections from the app host to unfamiliar destinations.
- Sudden spikes in errors from Server Components routes.
For public-facing sites, pair host-level checks with outside-in checks. Our guide on how to check if a website is hacked covers the signs visible from the outside, and what outside-in malware detection can and cannot see explains the limits. If you want alerts when headers or certificates on your sites change unexpectedly, Webforta Monitor covers that kind of drift, though it does not detect this vulnerability itself.
If you find evidence of compromise, follow website hacked: what to do and rebuild from a known-clean source rather than cleaning in place.
Timeline
| Date | Event |
|---|---|
| Oct 14, 2026 | Advisory published to the react/react repository |
| Nov 10, 2026 | Published to the GitHub Advisory Database, reviewed and last updated |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
