CVE-2026-126187: Unauthenticated RCE in React Server Components Flight Transport
CVE-2026-126187 is a critical unauthenticated remote code execution vulnerability in the React Server Components Flight transport implemented by react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack. It affects versions 19.0.0–19.0.8, 19.1.0–19.1.9, 19.2.0–19.2.8, and 19.3.0. In extremely rare configurations, responses containing multiple typed-array views sharing an underlying buffer and attacker-controlled data can suffer incorrect stream framing. Transferring the backing buffer can detach queued payload views, causing the writer to omit binary payload bytes while retaining their length headers. The reader can consequently interpret attacker-controlled bytes as Flight protocol rows, enabling unintended module execution or Server Action invocation. Applications without server-side React or without React Server Components integration are unaffected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise the confidentiality, integrity, and availability of the affected application through execution in its server-side or edge-rendering context. Injected protocol rows can trigger application-bundle module execution or invoke Server Actions with attacker-chosen arguments. Operating-system command execution through the Server Action path requires an action that handles those arguments dangerously. The vulnerability has a reported CVSS v4.0 base score of 9.5.
Mitigation
If you can’t patch tonight, do this now.
No vendor-supported workaround is identified; upgrading is recommended even when the rare triggering application pattern has not been found. As a temporary risk-reduction measure, avoid transporting multiple views sharing one ArrayBuffer in an RSC response, for example by copying each view into an independent backing buffer before serialization. This measure is not a substitute for patching.
Remediation
Patch, then assume compromise.
Upgrade affected react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack packages to the fixed release for their branch: 19.0.9, 19.1.10, 19.2.9, or 19.3.1, or a later patched release. Upgrade affected Next.js 16.0.0–16.4.0 applications to 16.4.1 or later; Next.js 15.5.28 also incorporates the transport fix. Because Next.js bundles its RSC implementation, verify the resolved Next.js version rather than relying solely on separately installed react-server-dom versions. Verify resolved dependencies, rebuild, and redeploy affected applications. The React fix copies large typed-array payloads into exact-size buffers to prevent writer-side framing corruption.
Exploits
3 exploits validated by Mallory's analysis.
References
Frequently asked questions
- Is CVE-2026-126187 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-126187 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-126187?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-126187, the earliest disclosed Nov 8, 2026.
- Is there a patch for CVE-2026-126187?
- Upgrade affected react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack packages to the fixed release for their branch: 19.0.9, 19.1.10, 19.2.9, or 19.3.1, or a later patched release. Upgrade affected Next.js 16.0.0–16.4.0 applications to 16.4.1 or later; Next.js 15.5.28 also incorporates the transport fix.
- How severe is CVE-2026-126187?
- CVE-2026-126187 has a CVSS v4 score of 9.5 (Critical) and an EPSS score of 1.8% (78th percentile) as of Nov 17, 2026.
Recent activity
42 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.