Updated 2026-11-15
Short answer: CVE-2026-126187 is an unauthenticated remote code execution bug in React Server Components, scored 9.5 (CVSS 4.0) in React's GitHub advisory. It affects 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. The fixed versions are 19.0.9, 19.1.10, 19.2.9 and 19.3.1, published on 10 November 2026. Next.js tracks the same bug as GHSA-673q-mjm6-r5xr. Next.js 16.0.0 to 16.4.0 are affected, and 16.4.1, released on 14 October 2026, fixes it (Next.js).
| Package | Affected | Fixed in |
|---|---|---|
| react-server-dom-webpack, -parcel, -turbopack | 19.0.0 to 19.0.8 | 19.0.9 |
| 19.1.0 to 19.1.9 | 19.1.10 | |
| 19.2.0 to 19.2.8 | 19.2.9 | |
| 19.3.0 | 19.3.1 | |
| next | 16.0.0 to 16.4.0 | 16.4.1 |
GitHub's advisory for Next.js lists no affected 15.x versions for this bug.
React says the bug "only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value". If an app's React code does not use a server, it is not affected. If it does not use a framework, bundler or bundler plugin that supports React Server Components, it is not affected either (GitHub advisory).
In Next.js the trigger is an App Router app with Cache Components where a use cache function returns multiple typed arrays. Next.js says there is no known workaround and that you should upgrade "even if your application does not have similar functions".
When React streams large typed arrays that share one buffer, and that buffer is handed off during the stream, the vulnerable writer (19.2.8 in StepSecurity's lab) silently drops the bytes of one view but keeps its header. The header still promises those bytes, so the client parser reads the next rows as the missing data. It then resumes parsing at an offset inside attacker-controlled bytes, where a planted module row makes the app load and run a module from its own bundle. StepSecurity reproduced the chain end to end against a real server render. The 19.2.9 writer copies large typed arrays into buffers of exact size, so a header is never left without its bytes (StepSecurity).
Run these in the project folder:
npm ls next react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack grep -A1 '"node_modules/next"' package-lock.json grep -n "cacheComponents" next.config.* grep -rln "use cache" app src 2>/dev/null
npm ls prints the versions that actually resolve, including transitive ones. For pnpm or Yarn, use pnpm why next or yarn why next. The next package does not list react-server-dom-webpack as an npm dependency (npm registry), so in a plain Next.js app the React package names may print nothing, and the next version is the one to compare with the table. cacheComponents: true in next.config turns on Cache Components, the feature behind use cache (Next.js docs).
When checked on 15 November 2026, GitHub's database entry for the Next.js advisory had no CVE ID. A scanner that only searches for CVE-2026-126187 may therefore flag the React packages and miss next.
On 11 November 2026 The Hacker News reported that proof-of-concept code is public. It also noted that the attack needs a specific Cache Components setup with multiple typed arrays, so not every React app is affected.
The 14 October out-of-band release (16.4.1 and 15.5.28) also fixed:
FixLane's page: public exploit for the React Server Components RCE in Next.js. NVD's facts: CVE-2026-126187.
Next.js 16.4.1, released on 14 October 2026, and later. Next.js 16.0.0 to 16.4.0 are affected. Next.js tracks it as GHSA-673q-mjm6-r5xr, and GitHub lists no affected 15.x versions.
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. Fixed: 19.0.9, 19.1.10, 19.2.9 and 19.3.1.
React says only extremely rare cases are affected, and apps with no server-side React are not. Next.js still says to upgrade even if your app has no such function.
The Hacker News reported on 11 November 2026 that proof-of-concept code is public.
Connect an AI agent to the free, read-only FixLane MCP server or ask the Telegram bot: it checks what you have installed against verified fixed versions and serves a reviewed fix procedure. All guides.