The Patch Shipped a Month Ago. 73% Are Still Vulnerable.
CVE-2026-126187 is an unauthenticated remote code execution flaw in React Server Components, rated 9.5 out of 10. The fix shipped on October 14, 2026. The CVE went public on November 10, and 73% of weekly downloads are still on affected versions. Here is what the flaw is, who it affects, and the four steps to fix it before the weekend.
Amir Ali Liaqat · Founder & CEO, DesignsToDeploy

On November 10, 2026, the CVE record for CVE-2026-126187 went public. It describes an unauthenticated remote code execution flaw in React Server Components, rated 9.5 out of 10 on the CVSS scale. The fix had already existed for almost a month: React shipped patched versions on October 14, and Next.js shipped its fix the same day. Within a day of the CVE publication, public proof-of-concept code appeared. And a November 11 read of npm downloads found that 73% of weekly react-server-dom-webpack downloads, 2.7 million of 3.8 million, were still on affected versions. The story here is not that a new bug appeared. It is that most of the ecosystem has not applied a fix that already exists.
What CVE-2026-126187 actually is
React Server Components move rendering to the server and stream the result to the client through Flight, a wire protocol that can carry far more than JSON: promises, module references, sets, form data, binary blobs, and typed arrays. The flaw sits in how Flight deserializes what it receives. The GitHub Advisory Database classifies it as CWE-502, deserialization of untrusted data. In the vulnerable versions, a cached response carrying two large typed-array views over one shared buffer could make the serializer announce bytes it never sent, and the deserializer would then trust the wrong bytes and resume parsing in the middle of attacker-influenced data. That is framing injection inside React's own serialization layer, the same bug class as HTTP request smuggling. The public proof of concept turns the parsing error into unauthenticated code execution by forging Flight rows that resolve to a real, registered Server Action with attacker-supplied arguments.
Why the trigger is rarer than the exposure
React's own advisory describes the trigger as extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value. That qualifier deserves a second look. Next.js 16's Cache Components change the trust picture: when a function marked use cache runs, its return value is serialized through the same Flight transport, stored as a cache entry, and deserialized back inside the Node.js server process on later requests. The deserializer is now handling data whose origin is a cache entry. The patch notes add that ordinary small Buffer allocations in Node are themselves partial views over a shared memory pool by construction, so an application does not need to write shared-buffer views explicitly for them to show up in a cached return value. That is why Vercel told everyone on an affected version to upgrade, even if they believed no such function existed in their codebase. The exact code shape is a property of the target, not a control defenders can rely on, and it can arrive through a dependency update or a routine refactor.
The timeline, and why the CVE date matters
On October 8, the Next.js team gave the ecosystem a week's notice that an out-of-band security release was coming. On October 14, React published advisory GHSA-xqc2-xf4c-x3h3 and backported fixes into four release lines at once, and Vercel shipped Next.js 16.4.1 on the Active LTS line and 15.5.28 on the maintenance line the same day. For almost four weeks the fix existed without a CVE number, which is structurally hard for tooling to catch: a plain dependency scan for react-server-dom-webpack comes back clean in Next.js applications, because the vulnerable code sits inside a compiled copy of React vendored into the framework itself. The CVE record was published on November 10, and within a day a working proof of concept with a reproducible Docker lab was public. The 73% figure comes from cve.now's November 11 read of npm: download counts include CI runs and mirrors, not just installs, so it measures ecosystem lag rather than the share of live sites, but the direction is unmistakable. As of November 10 to 11, no in-the-wild exploitation had been reported, and the flaw was not in CISA's Known Exploited Vulnerabilities catalog.
Who is affected, and what to upgrade to
- Affected: react-server-dom-webpack, react-server-dom-turbopack, and react-server-dom-parcel, versions 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, depending on your React line.
- Next.js: versions 16.0.0 to 16.4.0 with the App Router and Cache Components are affected (advisory GHSA-673q-mjm6-r5xr), fixed in 16.4.1. The November 3 releases, 16.4.5 and 15.5.29, carry seven further medium-severity fixes, so upgrade to those rather than stopping at the October releases.
- Not affected: applications whose React code does not use a server, or that use no framework, bundler, or bundler plugin supporting Server Components.
Four steps before the weekend
First, check. Open your lockfile and look for react-server-dom-webpack, -turbopack, or -parcel, and your Next.js version. Check the lockfile, not the dashboard: a plain dependency scan can miss the vendored copy inside Next.js. Second, upgrade. Install the fixed release for your React line, and move Next.js to 16.4.1 or later. Third, redeploy. Rebuild and ship the new build, because the vulnerable code is compiled into your deployment, so a version bump alone changes nothing until the new build is live. Fourth, watch. No exploitation has been reported yet, which is the time to patch, not the reason to wait. Keep an eye on exploitation reports and the CISA KEV catalog, and make patching a habit rather than a panic.
“No exploitation reported yet. That is the time to patch, not the reason to wait.”
What this means for your business
A critical patch is only useful if someone applies it, and the 73% figure shows how often nobody does. Security maintenance is not a one-off task: it is a standing habit of tracking advisories, keeping a maintenance window, and auditing after every release. For a business website, the cost of that habit is a fraction of the cost of an incident, and the check itself takes about half an hour. If your site runs on React or Next.js and nobody on your team owns the patching, that is exactly what our maintenance and support service covers: we audit the versions, apply the fixes, redeploy, and keep watching, so a CVE publication never becomes an emergency.
Sources: The CyberSec Guru, CVE-2026-126187: Next.js React Flight RCE Explained, November 12, 2026; Reef Sentinel, React Server Components RCE CVE-2026-126187 (CVSS 9.5), November 12, 2026; Meterpreter, React Server Components 19.3.1 Fixes CVE-2026-126187 Flaw, November 11, 2026; Penligent, CVE-2026-126187: React RSC RCE Exposure Checks, November 12, 2026; Brandefense, CVE-2026-126187: React Server Components RCE (CVSS 9.5), Fix, published November 8, updated November 11, 2026. The React advisory is GHSA-xqc2-xf4c-x3h3; the Next.js advisory is GHSA-673q-mjm6-r5xr. The 73% figure is cve.now's November 11 read of npm weekly downloads for react-server-dom-webpack (2.7 million of 3.8 million on affected versions); download counts include CI runs and mirrors. Proof-of-concept availability is reported by multiple outlets and was not independently verified by us. All claims observed November 13, 2026.
1 / 5Keep reading

CSS Grid vs Flexbox: The One Rule That Ends the Debate
Flexbox is one-dimensional, Grid is two-dimensional. The rule from the W3C spec editor who wrote both specifications, plus when each one wins, the nested pattern production sites actually use, and the code to prove it.
Read article
Tailwind CSS vs Bootstrap: Stop Picking Blind
Tailwind and Bootstrap both build modern UIs, but they think about CSS in opposite ways. Here is the real difference between utility-first and component-first styling, what changed in Tailwind v4 and the Bootstrap 6 alpha, and the decision rules we use to pick one for a project.
Read article
Static and Personal, on the Same Page: Next.js 16.4 and Cache Components
Next.js 16.4 makes Cache Components the recommended caching model for every Next.js app. One page can now mix cached and personal content, per component. Here is what 'use cache' changes, the three-step adoption plan, and why you should upgrade to 16.4.1 first.
Read article