1-minute read of a 5 min report

React Flight Framing Flaw Lets Attackers Run Code in Server Apps

By

1-minute read

What a defender needs to know

React fixed CVE-2026-126187, an unauthenticated code-execution flaw in the Flight transport used by React Server Components frameworks. The React advisory says it requires a rare response containing multiple typed arrays and an attacker-controlled value. Client-only React apps and apps without an RSC-capable framework or plugin are outside the affected scope.

StepSecurity researcher Owais Shaikh reproduced the chain in a lab: detaching a shared buffer left a binary row’s length header without its bytes. The Flight parser consumed following rows as data, then interpreted attacker-influenced bytes as a module row. Shaikh observed the patched writer copy the large typed-array data instead. Production exposure depends on whether an application’s consumer transfers the backing buffer.

Check resolved versions of react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack in server-rendered apps. Fixed releases are 19.0.9, 19.1.10, 19.2.9, and 19.3.1 for their respective release lines, according to the CVE record. Upgrade the framework or direct dependency, rebuild, and verify the running server bundle’s resolved version. Until then, avoid sending multiple views of one shared ArrayBuffer through Flight. When response bodies are retained, investigate binary rows whose declared length exceeds the available bytes and correlate client Connection closed errors with large typed-array responses; neither signal alone identifies an attack.

Primary sources