Unauthenticated RCE in React Server Components

Red | Vulnerability
Unauthenticated RCE in React Server Components | Hive Pro Threat Advisory
Date of publication
November 10, 2026
Admiralty code
A1
TA number
TA2026332
First seen
October 14, 2026
Affected products
React Server Components (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack), Vercel Next.js

Summary

Successful exploitation of this React Server Components flaw allows a remote, unauthenticated attacker to run server-side functions within an affected application. The resulting damage depends on the Server Actions exposed, which commonly handle orders, account changes, record updates, file operations, and calls to internal services. This can lead to data theft, tampering with business records, and a foothold into connected back-end systems.

As React Server Components and Next.js commonly power customer-facing websites, storefronts, and SaaS platforms, and a public exploit lowers the skill required to attack them, the business risk is high for organizations running unpatched applications despite the narrow trigger conditions.

CVENameAffected product
UnassignedReact Server Components Typed Array Deserialization Remote Code Execution Vulnerability (GHSA-xqc2-xf4c-x3h3)React Server Components (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack)

Vulnerability Details

#1

A critical unauthenticated remote code execution vulnerability in the React Server Components (RSC) serializer, the component that encodes and decodes server-rendered and cached data. React has not assigned a CWE; it is assessed here as CWE-502 (Deserialization of Untrusted Data).

#2

The flaw stems from improper handling of typed arrays during deserialization. When a cached response contains multiple typed-array views over a single shared ArrayBuffer, the RSC decoder becomes desynchronized from the serialized stream. An attacker-controlled value in the same response is then treated as trusted content, allowing the decoder to be steered into invoking a Server Action with attacker-supplied arguments.

#3

Exploitation requires a response that carries multiple typed arrays alongside an attacker-controlled value, a condition React describes as extremely rare. In Next.js, this corresponds to a "use cache" function returning multiple typed arrays and user-influenced data on a cached page that can resolve a Server Action. The attack is delivered over the network through a crafted request, and its impact depends on the Server Action invoked. As the defect resides in React's serializer, securely written application code can still be exposed.

#4

React rates the issue Critical with a CVSS v4.0 score of 9.5, reflecting network exploitability, low attack complexity, no required privileges or user interaction, and high impact on the vulnerable and connected systems.

#5

Affected versions of react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack are 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 in 19.0.9, 19.1.10, 19.2.9, and 19.3.1. Next.js 16.0.0 to 16.4.0 using the App Router with Cache Components is also affected and is fixed in 16.4.1. Applications that do not use a server, or a framework, bundler, or bundler plugin supporting React Server Components, are not affected.

Affected products, CPE and CWE
CVE IDAffected productsAffected CPECWE ID
UnassignedReact 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 react-server-dom-parcel (same versions); React react-server-dom-turbopack (same versions); Vercel Next.js (16.0.0 to 16.4.0, App Router with Cache Components)cpe:2.3:a:facebook:react-server-dom-webpack:*:*:*:*:*:node.js:*:*cpe:2.3:a:facebook:react-server-dom-parcel:*:*:*:*:*:node.js:*:*cpe:2.3:a:facebook:react-server-dom-turbopack:*:*:*:*:*:node.js:*:*cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*CWE-502

Recommendations

  1. 01

    Upgrade React Server Components Packages

    Update react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack to 19.0.9, 19.1.10, 19.2.9, 19.3.1, or later. React provides no workaround and recommends upgrading immediately, so prioritize internet-facing applications built on Server Components.

  2. 02

    Upgrade Next.js Deployments

    Update Next.js 16.0.0 through 16.4.0 to 16.4.1 or later, prioritizing applications that use the App Router with Cache Components. Rebuild and redeploy so the patched RSC runtime is included in production artifacts.

  3. 03

    Verify the Fix in Deployed Builds

    Search the react-server-dom-webpack server production bundle for the getBackingBlob marker across container images, serverless bundles, and cached build outputs. Zero matches indicates a build that is still vulnerable.

  4. 04

    Apply Interim Mitigations

    Where patching is delayed, remove or refactor "use cache" functions that return multiple typed arrays together with attacker-controlled values. Enforce server-side authentication, authorization, and input validation within every Server Action to limit the impact of any unauthorized invocation.

  5. 05

    Monitor for Exploitation Attempts

    Review web server, CDN, and application logs for requests with unusually long base64-encoded query parameters and for responses containing serialized Server Action output. Configure WAF or reverse-proxy rules to flag such requests to RSC-rendered routes, and escalate suspicious activity to incident response.

  6. 06

    Strengthen Vulnerability Management

    Maintain a software bill of materials covering direct and transitive dependencies on React Server Components and frameworks such as Next.js. Track vendor security advisories and prioritize critical fixes even when no CVE has been assigned.


Potential MITRE ATT&CK TTPs

Reconnaissance
T1594Search Victim-Owned Websites
Initial Access
T1190Exploit Public-Facing Application
Execution
T1059Command and Scripting Interpreter
T1059.007JavaScript

References & Patch Links

Patch links
References

What Next?

At Hive Pro, it is our mission to detect the most likely threats to your organization and to help you prevent them from happening.

Reduce real exposure. Not just vulnerability volume.