---
title: "React Server Components RCE: CVE-2026-126187"
url: https://erroneo.us/security/briefs/react-server-components-typed-array-rce-cve-2026-126187/
description: "Critical unauthenticated RCE in react-server-dom-* 19.0.0 to 19.3.0. Fixed in 19.0.9, 19.1.10, 19.2.9, 19.3.1 and Next.js 16.4.1. Narrow trigger."
type: security-brief
section: "Security Digest"
date_published: 2026-11-10
date_modified: 2026-11-11
publisher: erroneo.us
author: erroneo.us Security Desk
verdict: "Patch this week"
cves: ["CVE-2026-126187"]
severity: "critical"
exploited: "none-known"
kev: false
license: All rights reserved. Quote with attribution and a link.
---

# React Server Components RCE: CVE-2026-126187

**Verdict: Patch this week.** The fix has been on npm since October 14 and the React team says the trigger is extremely rare, so this is a routine but prompt upgrade for anyone running React Server Components, not an emergency.

- **Who must act:** Teams running React Server Components on a server: Next.js 16.0.0 through 16.4.0 with the App Router, and any app that depends on react-server-dom-webpack, -turbopack or -parcel 19.0.0 through 19.3.0.
- **Who can relax:** Client-only React apps, apps with no framework or bundler that supports Server Components, and anyone already on the fixed React packages or Next.js 16.4.1 or later.
- **Affected:** react-server-dom-webpack 19.0.0 to 19.0.8, 19.1.0 to 19.1.9, 19.2.0 to 19.2.8, 19.3.0; 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, 19.3.0; react-server-dom-parcel 19.0.0 to 19.0.8, 19.1.0 to 19.1.9, 19.2.0 to 19.2.8, 19.3.0; Next.js 16.0.0 through 16.4.0 (GHSA-673q-mjm6-r5xr)
- **Fixed:** react-server-dom-webpack and -turbopack 19.0.9, 19.1.10, 19.2.9, 19.3.1; react-server-dom-parcel 19.1.10, 19.2.9, 19.3.1 (no 19.0.9 on npm as of Nov 11, 2026); Next.js 16.4.1 or later (latest is 16.4.6)
- **CVEs:** CVE-2026-126187
- **CISA KEV:** no · **Exploitation:** No known exploitation

## What to do

1. Run npm ls react-server-dom-webpack react-server-dom-turbopack react-server-dom-parcel next and compare the versions with the fixed releases.
2. On Next.js 16, upgrade to 16.4.1 or later with npm install next@latest, then rebuild and redeploy.
3. If you depend on the react-server-dom-* packages directly, move to 19.0.9, 19.1.10, 19.2.9 or 19.3.1 on your release line and keep react and react-dom on the matching version.
4. On react-server-dom-parcel 19.0.x, move to 19.1.10 or later, because no 19.0.9 was published for that package.
5. Redeploy every environment built from the old lockfile, including preview and staging servers that are reachable from the internet.

### How to check if you are affected

- Check what is actually deployed, not only the repository: run npm ls next react-server-dom-webpack in the build image or read the next version from the running container's node_modules/next/package.json.
- Search your code for 'use cache' functions and Server Component responses that return typed arrays (Uint8Array, Float32Array and similar). Those are the paths the advisories describe.
- No indicators of compromise or exploit details have been published as of Nov 11, 2026. If you ran an affected version on the internet, review server logs for unexpected child processes and outbound connections from the Node.js process.

## What happened

On November 10, 2026, GitHub published [CVE-2026-126187](https://www.cve.org/CVERecord?id=CVE-2026-126187) and the reviewed advisory [GHSA-xqc2-xf4c-x3h3](https://github.com/advisories/GHSA-xqc2-xf4c-x3h3) for a critical flaw in React Server Components. The [React advisory](https://github.com/react/react/security/advisories/GHSA-xqc2-xf4c-x3h3) says "crafted payloads targeting frameworks supporting React Server Components can lead to remote code execution." No login is required. The CVE record classifies it as deserialization of untrusted data (CWE-502) and scores it 9.5 on CVSS 4.0.

The bug is in the three packages that implement the Server Components wire protocol: `react-server-dom-webpack`, `react-server-dom-turbopack` and `react-server-dom-parcel`, 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.

The fix is not new. The patched releases went to npm on October 14, 2026, four weeks before the CVE. The [19.3.1 release notes](https://github.com/react/react/releases/tag/v19.3.1) describe the change only as "Improve transport protocol." Next.js shipped its side of the fix the same day in [16.4.1](https://github.com/vercel/next.js/releases/tag/v16.4.1), and its own advisory, [GHSA-673q-mjm6-r5xr](https://github.com/vercel/next.js/security/advisories/GHSA-673q-mjm6-r5xr), has been public since October 22. What changed on November 10 is that the React-level issue received a CVE, so scanners now flag it.

## Who is affected

Apps that render React Server Components on a server and use one of the affected package versions. In practice that mostly means Next.js. The Next.js advisory lists versions 16.0.0 through 16.4.0 as affected and describes the vulnerable case as "applications using App router with Cache Component" that have "a `use cache` function that returns multiple typed arrays." It does not list Next.js 15 or earlier.

Other frameworks and bundler plugins that build on the `react-server-dom-*` packages inherit the bug through those packages. Neither advisory names any of them, so check your lockfile.

The React advisory is explicit about who is not affected: "If an app's React code does not use a server, the app is not affected," and the same holds if the app "does not use a framework, bundler, or bundler plugin that supports React Server Components." A single-page app served as static files is out of scope.

## Do you really need to act?

**Yes if you run Server Components, but this is a scheduled upgrade, not an incident.** Three things keep the risk lower than the 9.5 score suggests.

- **The trigger is narrow.** The React team says the bug "only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value." The CVSS vector reflects this with AT:P, meaning a precondition must exist in the target app. Most apps never send typed arrays through a Server Component response.
- **No exploitation is known.** The CVE is not in CISA's KEV catalog as of the November 10 catalog, and neither advisory mentions attacks or a public proof of concept.
- **The fix is a month old.** Teams that kept Next.js 16 current after mid-October are already patched.

The reasons not to ignore it are just as plain. The impact is code execution on your server without authentication. It is hard to prove that none of your code or dependencies ever combine typed arrays with user input. The patch has been public for four weeks, which gives attackers time to study it. Next.js says there is "no known workaround" and tells users to "upgrade immediately even if your application does not have similar functions."

## What to do now

1. List what you have: `npm ls react-server-dom-webpack react-server-dom-turbopack react-server-dom-parcel next`. With pnpm, use `pnpm why next`.
2. On Next.js 16, upgrade to 16.4.1 or later: `npm install next@latest`. The latest release on November 11 is 16.4.6.
3. Next.js ships its own compiled copy of the Server Components runtime, so a lockfile search for `react-server-dom-webpack` can come back empty on a vulnerable app. Decide by the `next` version.
4. If you depend on the packages directly, install the fixed release on your line, for example `npm install react-server-dom-webpack@19.2.9 react@19.2.9 react-dom@19.2.9`.
5. On `react-server-dom-parcel` 19.0.x, move to 19.1.10 or later. The advisory lists 19.0.9 as the fix, but the [npm registry](https://registry.npmjs.org/react-server-dom-parcel) had no 19.0.9 for that package on November 11.
6. Rebuild and redeploy every environment, including previews.

## How to tell if you were hit

Nothing has been published that would let you identify an attack: no exploit details, no request signatures and no indicators of compromise as of November 11, 2026. Start with exposure. If no affected version was reachable from the internet, or your code never returns typed arrays from Server Components or `use cache` functions, there is little to investigate.

If you did run an affected version with that pattern, look at the Node.js server process over the exposure window for child processes it should not start, such as shells or download tools, and for unexpected outbound connections. Rotate the secrets available to that process if you find anything.

## Timeline

- Oct 14, 2026 — React publishes 19.0.9, 19.1.10, 19.2.9 and 19.3.1 to npm. Next.js releases 16.4.1 with the fix.
- Oct 22, 2026 — The Next.js advisory GHSA-673q-mjm6-r5xr appears in the GitHub Advisory Database.
- Nov 10, 2026 — CVE-2026-126187 is published and GHSA-xqc2-xf4c-x3h3 is added to the GitHub Advisory Database, rated critical.
- Nov 11, 2026 — No known exploitation and no KEV listing.

## Sources

1. [React — GHSA-xqc2-xf4c-x3h3: Unauthenticated Remote Code Execution in React Server Components](https://github.com/react/react/security/advisories/GHSA-xqc2-xf4c-x3h3)
2. [CVE.org — CVE-2026-126187](https://www.cve.org/CVERecord?id=CVE-2026-126187)
3. [GitHub Advisory Database — GHSA-xqc2-xf4c-x3h3](https://github.com/advisories/GHSA-xqc2-xf4c-x3h3)
4. [Next.js — GHSA-673q-mjm6-r5xr: Unauthenticated Remote Code Execution in use cache functions returning typed arrays](https://github.com/vercel/next.js/security/advisories/GHSA-673q-mjm6-r5xr)
5. [Next.js — v16.4.1 release notes](https://github.com/vercel/next.js/releases/tag/v16.4.1)
6. [React — v19.3.1 release notes](https://github.com/react/react/releases/tag/v19.3.1)
7. [npm registry — react-server-dom-parcel version list](https://registry.npmjs.org/react-server-dom-parcel)

---
Source page: https://erroneo.us/security/briefs/react-server-components-typed-array-rce-cve-2026-126187/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt
