NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-126187: React: Unauthenticated Remote Code Execution in React Server Components

criticalCVSS 4.0 9.5GHSA-xqc2-xf4c-x3h3

Crafted requests to React Server Components servers can give an unauthenticated attacker remote code execution. The flaw is in react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack 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. Upgrade to 19.0.9, 19.1.10, 19.2.9 or 19.3.1.

Published Nov 10, 2026 · Analysis Nov 12, 2026

What an attacker can do

React Server Components decode data sent by clients on the server. A crafted payload can turn that decoding into code execution (CWE-502, deserialization of untrusted data). The advisory says this affects only extremely rare cases where responses transport multiple typed arrays together with an attacker-controlled value. It does not explain the root cause further.

The CVSS 4.0 vector shows network access, low complexity, no privileges and no user interaction. The one precondition is the rare typed-array pattern, which is why attack requirements are rated present. If the pattern exists in your app, an attacker needs only to send a request to the server endpoint. The result is code execution on the server with high impact on confidentiality, integrity and availability, which exposes environment secrets, database access and cloud credentials.

Apps without a server, or without a framework, bundler or bundler plugin that supports React Server Components, are not affected. Check which versions your framework pulls in. The advisory credits evolutionstorm.

Who is affected

These three npm packages are affected in these ranges: 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:

  • react-server-dom-webpack
  • react-server-dom-parcel
  • react-server-dom-turbopack

Check what you have installed, including copies pulled in by your framework:

npm ls react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack

react-server-dom-parcel

Ecosystem
npm
Affected
>= 19.0.0, < 19.0.9
Fixed in
19.0.9
Check
npm ls react-server-dom-parcel

react-server-dom-parcel

Ecosystem
npm
Affected
>= 19.1.0, < 19.1.10
Fixed in
19.1.10
Check
npm ls react-server-dom-parcel

react-server-dom-parcel

Ecosystem
npm
Affected
>= 19.2.0, < 19.2.9
Fixed in
19.2.9
Check
npm ls react-server-dom-parcel

react-server-dom-parcel

Ecosystem
npm
Affected
>= 19.3.0, < 19.3.1
Fixed in
19.3.1
Check
npm ls react-server-dom-parcel

react-server-dom-turbopack

Ecosystem
npm
Affected
>= 19.0.0, < 19.0.9
Fixed in
19.0.9
Check
npm ls react-server-dom-turbopack

react-server-dom-turbopack

Ecosystem
npm
Affected
>= 19.1.0, < 19.1.10
Fixed in
19.1.10
Check
npm ls react-server-dom-turbopack

react-server-dom-turbopack

Ecosystem
npm
Affected
>= 19.2.0, < 19.2.9
Fixed in
19.2.9
Check
npm ls react-server-dom-turbopack

react-server-dom-turbopack

Ecosystem
npm
Affected
>= 19.3.0, < 19.3.1
Fixed in
19.3.1
Check
npm ls react-server-dom-turbopack

react-server-dom-webpack

Ecosystem
npm
Affected
>= 19.0.0, < 19.0.9
Fixed in
19.0.9
Check
npm ls react-server-dom-webpack

react-server-dom-webpack

Ecosystem
npm
Affected
>= 19.1.0, < 19.1.10
Fixed in
19.1.10
Check
npm ls react-server-dom-webpack

react-server-dom-webpack

Ecosystem
npm
Affected
>= 19.2.0, < 19.2.9
Fixed in
19.2.9
Check
npm ls react-server-dom-webpack

react-server-dom-webpack

Ecosystem
npm
Affected
>= 19.3.0, < 19.3.1
Fixed in
19.3.1
Check
npm ls react-server-dom-webpack

How to fix it

Upgrade to the patched release in your line: 19.0.9, 19.1.10, 19.2.9 or 19.3.1. For example:

npm install [email protected]

Use the matching package name for Parcel or Turbopack. If a framework pulls these packages in, upgrade the framework to a release that depends on a fixed version, and check the lockfile. The advisory's Patches section writes 19.0.09, which is a typo for 19.0.9. The advisory lists no workaround and recommends updating immediately.

How to tell if you were hit

The advisory gives no indicators. Review server logs for unusual or malformed POST requests to Server Function or RSC endpoints, followed by unexpected child processes, outbound connections or new files on the app server.

Check your lockfile history to see how long a vulnerable version was deployed. If the server was exposed on a vulnerable version, rotate secrets that the process could read, such as environment variables and cloud credentials.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Impact

Crafted payloads targeting frameworks supporting React Server Components can lead to remote code execution. This only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value.

Updating immediately is recommended.

The vulnerability exists in versions 19.0.0 through 19.0.8, 19.1.0 through 19.1.9, 19.2.0 through 19.2.8 and 19.3.0 of:

  • react-server-dom-webpack
  • react-server-dom-parcel
  • react-server-dom-turbopack

Patches

Fixes were back ported to versions 19.0.09, 19.1.10, 19.2.9, and 19.3.1.

If applications are using any of the above packages please upgrade to any of the fixed versions immediately.

If an app’s React code does not use a server, the app is not affected by this vulnerability. If an app does not use a framework, bundler, or bundler plugin that supports React Server Components, the app is not affected by this vulnerability.

Credited to evolutionstorm.

Questions

Is my React app affected by CVE-2026-126187?

Only if it runs a server with a framework, bundler or plugin that supports React Server Components and uses an affected version of one of the three react-server-dom packages. Client-only apps are not affected.

Does it need authentication?

No. The vector shows no privileges and no user interaction. The advisory notes the trigger is rare: responses carrying multiple typed arrays and an attacker-controlled value.

Which versions fix it?

19.0.9, 19.1.10, 19.2.9 and 19.3.1, depending on your release line.

Is it exploited in the wild?

The advisory does not say so, and the entry has no CISA KEV data.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

Coverage on the Beam blog

More npm vulnerabilities

All npm entries