Vulnerability DatabaseCVE-2026-126187

CVE-2026-126187: 
React Server Components vulnerability analysis and mitigation

Overview

CVE-2026-126187 is a critical unauthenticated Remote Code Execution (RCE) vulnerability in React's Server Components transport layer, specifically affecting the react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack packages. The flaw exists in React versions 19.0.0–19.0.8, 19.1.0–19.1.9, 19.2.0–19.2.8, and 19.3.0, and was disclosed via GitHub Security Advisory GHSA-xqc2-xf4c-x3h3 on November 10, 2026. It only affects applications using a server-side framework or bundler plugin that supports React Server Components (RSC), and does not impact client-only React apps. The vulnerability carries a CVSS v4.0 base score of 9.5 (Critical) (GitHub Advisory).

Technical details

The root cause is improper deserialization of untrusted data (CWE-502) within the React Flight protocol — the binary transport used by React Server Components. When a server response transports multiple typed arrays sharing an underlying ArrayBuffer, an attacker-controlled value can cause a "typed-array framing desync": the decoder's read position is manipulated so that attacker-supplied bytes are parsed as legitimate React Flight rows. These forged rows can reference a Server Action ID with attacker-chosen arguments, causing the server to invoke that action and return its output. Exploitation requires no authentication or user interaction, but does require the target to be running a framework (e.g., Next.js) with RSC and use cache or similar caching features enabled, and that the response path involves multiple typed arrays alongside an attacker-controlled value (GitHub Advisory, Feedly). The fix, described as "[Flight] Improve transport protocol," hardens binary data writing by copying large partial buffer views instead of transmitting the whole underlying buffer, and throws on detached buffers (React PR #37842, React PR #37845).

Impact

Successful exploitation grants an unauthenticated remote attacker the ability to execute arbitrary server-side commands with the privileges of the Node.js process running the React application. This results in full compromise of confidentiality (access to secrets, environment variables, source code, and data), integrity (arbitrary file writes, code injection), and availability (process termination, resource exhaustion). Because Server Actions can interact with databases, internal APIs, and cloud credentials, exploitation may enable lateral movement into backend infrastructure. Applications not using server-side React or RSC-capable frameworks are entirely unaffected (GitHub Advisory).

Exploitability

Multiple public proof-of-concept exploits are available on GitHub, including Python and Node.js implementations targeting Next.js and react-server-dom-webpack environments (briskets PoC, rudSarkar PoC, TahuCryptsi PoC). The exploits are dependency-free, operate unauthenticated over the network, and auto-discover Server Action IDs from target pages. As of the advisory date, no confirmed in-the-wild exploitation has been reported, and the CVE status is listed as "Deferred" with NVD SSVC exploitation rated "none" (Feedly). The EPSS score is approximately 0.0176 (~1.76%), and the vulnerability is not currently listed in the CISA KEV catalog.

Exploitation steps

  1. Reconnaissance: Identify target applications running Next.js or another RSC-capable framework with react-server-dom-webpack, react-server-dom-parcel, or react-server-dom-turbopack in the vulnerable version range (19.0.0–19.0.8, 19.1.0–19.1.9, 19.2.0–19.2.8, 19.3.0). Use tools like Shodan, Censys, or passive DNS to find internet-facing instances.
  2. Discover Server Action ID: Fetch the target page and regex-search the HTML for $ACTION_ID_<40+ hex chars>. If not found inline, fetch referenced <script src> bundles and search for createServerReference followed by a 40+ hex string. Alternatively, supply a known action ID via --action-id (TahuCryptsi PoC).
  3. Construct forged Flight rows: Build three React Flight protocol rows: 6:<json args> (attacker-chosen command arguments), 5:{"id":"<action_id>","bound":"$@6"} (Server Action reference), and <chunk_id>:{"then":"$h5"} (thenable root trigger) (briskets PoC).
  4. Build the padded annotation blob: Create a buffer of filler bytes (F or P) sized to the overread parameter. Write a length header (<chunk_id>:o<hex length>,) and place the forged rows at offset overread - len(header), exploiting the typed-array framing desync so the decoder resumes parsing at the attacker-controlled rows.
  5. Deliver the payload: Base64-encode the blob, URL-encode it, and issue an unauthenticated GET request to <target_path>?annotation=<encoded_blob> (or POST to a profile/display-name endpoint, depending on the exploit variant).
  6. Extract command output: Parse the response for a <pre> JSON block and read the annotation key. Non-empty, non-null values indicate successful Server Action invocation with attacker-chosen arguments.
  7. Optional parameter scan: If the default chunk ID and overread values fail, use --scan to brute-force chunk IDs (1–8) and overread sizes (1024–32768) until execution is confirmed (TahuCryptsi PoC).

Indicators of compromise

  • Network: Unusual GET requests to RSC-enabled page paths with a large, base64-encoded annotation= query parameter; POST requests to profile or display-name endpoints with oversized text/plain bodies containing repeated padding characters (F or P) followed by JSON-like Flight rows; unexpected outbound connections from the Node.js server process to attacker-controlled IPs.
  • Logs: Web server access logs showing requests with ?annotation= parameters containing long base64 strings; repeated requests to the same RSC page path with varying annotation values (indicative of parameter scanning); HTTP 200 responses to anomalous query strings on cached RSC routes.
  • Process: Unexpected child processes spawned by the Node.js server process (e.g., sh, bash, id, whoami, curl, wget); unusual process execution chains originating from the framework's server runtime.
  • File System: New or modified files in the application directory created by the Node.js process user; unexpected scripts or binaries written to /tmp or the app working directory.
  • Application: Server Action invocations with arguments not originating from legitimate client sessions; JSON responses containing command output (e.g., uid=, root) in the annotation field of RSC payloads.

Mitigation and workarounds

Upgrade the affected packages immediately to the patched versions: 19.0.9, 19.1.10, 19.2.9, or 19.3.1, depending on your version track (GitHub Advisory). The fix hardens the React Flight transport protocol to prevent typed-array framing desync by copying large partial buffer views and rejecting detached buffers (React PR #37842). If immediate upgrade is not possible, consider disabling RSC-specific caching features (e.g., use cache) or placing a WAF rule to block requests with anomalously large or base64-encoded annotation query parameters. Applications that do not use a server, or do not use a framework/bundler supporting React Server Components, are not affected and require no action.

Community reactions

The React core team published the advisory and patches simultaneously on October 14, 2026, with the security fix described as "[Flight] Improve transport protocol" across all maintained release branches (React PR #37842). Security researchers and the community noted the vulnerability's novelty — exploiting a binary protocol desync rather than a classic injection — with coverage appearing on Infosec.exchange, Mastodon, and security blogs including meterpreter.org and thecybersecguru.com (Feedly). StepSecurity published a dedicated technical blog post analyzing the React Flight RCE, and Cloudflare Radar referenced the issue under the codename "zero-wire." Multiple PoC repositories appeared within 24 hours of the advisory's public disclosure, reflecting high community interest.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Ubuntu

Unknown

bionic (esm-apps)

react

Unknown

devel

react

Unknown

focal (esm-apps)

react

Unknown

jammy

react

Unknown

jammy (esm-apps)

react

Unknown

noble

react

Unknown

noble (esm-apps)

react

Unknown

resolute

react

Unknown

RHEL / CentOS

Affected

RHEL 8

Not Affected

RHEL 9

Not Affected

RHEL 10

Not Affected

Source: This report was generated using AI

Related React Server Components vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-126187CRITICAL9.5
  • React Server Components logoReact Server Components
  • grafana-selinux
NoYesNov 10, 2026
GHSA-xqc2-xf4c-x3h3CRITICAL9.5
  • React Server Components logoReact Server Components
  • react-server-dom-turbopack
NoYesNov 10, 2026
CVE-2026-44907HIGH7.5
  • React Server Components logoReact Server Components
  • @vitejs/plugin-rsc
NoYesJul 21, 2026
CVE-2026-23870HIGH7.5
  • React Server Components logoReact Server Components
  • react-server-dom-parcel
NoYesMay 06, 2026
CVE-2026-23869HIGH7.5
  • React Server Components logoReact Server Components
  • next
NoYesApr 08, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management