Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilityinternet-facing-service-vulnerability

Critical React Server Components Flaw Enables Unauthenticated Remote Code Execution

Vulnerability Disclosure · 19 sources · Updated 4d ago · First seen Nov 9, 2026

Critical React Server Components Flaw Enables Unauthenticated Remote Code Execution

React disclosed a critical React Server Components vulnerability, tracked as GHSA-xqc2-xf4c-x3h3, that can enable unauthenticated remote code execution. The advisory assigns a CVSS v4 score of 9.5 and affects specific releases of react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack. Exploitation requires an extremely rare response pattern involving multiple typed arrays and attacker-controlled data, rather than simply the presence of React Server Components.

React recommends immediately upgrading affected packages to the appropriate fixed release: 19.0.9, 19.1.10, 19.2.9, or 19.3.1. Applications without server-side React code or React Server Components support are not affected. Security teams should inventory deployments using the affected packages and prioritize upgrades where vulnerable releases are present. The public advisory lists no known CVE identifier and makes no claim of active exploitation; this vulnerability is distinct from React2Shell, CVE-2025-55182.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Oct 14, 2026 – Nov 10, 2026
  1. Reported Nov 12, 20265d ago

    StepSecurity reproduces Flight module injection and verifies writer-side fix

    StepSecurity reports reproducing application-bundle module execution using React 19.2.8 renderToPipeableStream output and a simulated backing-store transfer. Testing found that 19.2.9 preserved binary payload framing, but its parser still executed planted module rows in deliberately corrupted input, demonstrating that the fix prevents writer-side corruption rather than rejecting injected rows.

    CVE-2026-126187: React Server Components Flaw Lets Attackers Execute Code Through Smuggled Flight Rows - StepSecurity
  2. Reported Nov 11, 20266d ago

    Public exploit code emerges for React Server Components RCE

    Public exploit code became available for CVE-2026-126187, a CVSS 9.5 React Server Components vulnerability that could allow unauthenticated remote code execution in certain Next.js applications. The reported attack requires a specific Cache Components configuration.

    TheHackersNews: ‼️ Public exploit code is out for a critical React Server Components RCE flaw affecting certain Next.js apps. CVE-2026-...
  3. Reported Nov 10, 20267d ago

    Technical analysis details React Flight deserialization and stream-buffer fixes

    Technical analysis identified remediation commits 61aa00df822d0eb76d0362eb8b6fdd3527693efe and 0c9913ae87283f96e868a8f1c20a3389827632d0, detailing restrictions on thenable execution, server-reference validation, and private Symbol protection for internal response references. Stream changes clone buffers where needed to prevent sibling-view detachment, detect detached buffers, and namespace multipart stream fields to prevent identifier collisions.

    CVE-2026-126187: CVE-2026-126187: Unauthenticated Remote Code Execution in React Server Components | CVEReports
  4. Nov 10, 20268d ago

    GitHub Advisory Database addition enables automated warnings for affected RSC packages

    React advisory GHSA-xqc2-xf4c-x3h3 was added to the GitHub Advisory Database under CVE-2026-126187. Following the addition, npm audit and Dependabot flag affected react-server-dom packages.

    React Server Components typed-array RCE | Zero Wire | Cloudflare Radar
  5. Oct 14, 20261mo ago

    Next.js releases 16.4.1 to fix bundled React Server Components runtime

    Next.js released version 16.4.1 less than an hour after React's advisory, fixing GHSA-xqc2-xf4c-x3h3 in its bundled runtime; versions 16.0.0 through 16.4.0 were listed as affected. Vercel stated there was no workaround and urged upgrades even for applications not using use cache, since updating react and react-dom alone does not replace the vulnerable bundled code.

    GHSA-xqc2-xf4c-x3h3: What the React Server Components Typed-Array RCE Means for Your Next.js Apps - Upwind
  6. Oct 14, 20261mo ago

    React discloses critical unauthenticated RCE flaw in Server Components

    React published advisory GHSA-xqc2-xf4c-x3h3, describing a CVSS v4 9.5 remote code execution vulnerability in react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack that requires an extremely rare response pattern involving multiple typed arrays and attacker-controlled data. The advisory identified fixed versions 19.0.9, 19.1.10, 19.2.9, and 19.3.1 and urged immediate upgrades, without claiming active exploitation.

    Critical React Server Components Flaw Lets Hackers Execute Code Remotely Without Authentication | Cryptika Cybersecurity
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Next.Js
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.