← All security briefings

Attention

React RSC typed-array flaw enables remote code execution in Next.js 16

Identifiers: GHSA-xqc2-xf4c-x3h3 · GHSA-673q-mjm6-r5xr · CVE-2026-126187

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

A payload framing defect in the React Server Components Flight transport (react-server-dom-webpack, -turbopack, -parcel) can, in extremely rare responses containing multiple typed arrays and an attacker-controlled value, lead to unauthenticated server code execution. Next.js 16.0.0 to 16.4.0 is affected when App Router, Cache Components, and a use cache function returning multiple typed arrays are combined. Client-only React without server or RSC support is out of scope. The React advisory now carries CVE-2026-126187.

Classification reason: Checked as of 12 November 2026. The advisories were published on 14 October 2026, so this is not a new vulnerability; CVE-2026-126187 was published by the GitHub CNA on 10 November 2026, which changes tracking, not scope. ZeroWire's review dates, including its earlier 8 November 2026 entry, are review dates, not publication or exposure proof.

Impact

Worst case is unauthenticated server code execution. Exposure requires an application returning multiple typed arrays; the public lab chain also needed a dangerous Server Action, so not every React app is affected.

Who is affected

Affected react-server-dom packages: 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 is fixed in 16.4.1. Next.js 15.x is not listed as affected by this advisory; the official post recommends 15.5.28, which carries the upstream transport fix plus a separate image fix. The React advisory GHSA-xqc2-xf4c-x3h3 now carries CVE-2026-126187 and was confirmed in GitHub's global advisory database at review; what npm audit actually reports was not tested, so a clean audit is not clearance. The Next.js advisory GHSA-673q-mjm6-r5xr still has no CVE.

Products and versions

Products and versionsAffectedFixed
react-server-dom-webpack 19.0.0–19.0.8; 19.1.0–19.1.9; 19.2.0–19.2.8; 19.3.0 19.0.9; 19.1.10; 19.2.9; 19.3.1
react-server-dom-turbopack 19.0.0–19.0.8; 19.1.0–19.1.9; 19.2.0–19.2.8; 19.3.0 19.0.9; 19.1.10; 19.2.9; 19.3.1
react-server-dom-parcel 19.0.0–19.0.8; 19.1.0–19.1.9; 19.2.0–19.2.8; 19.3.0 19.0.9; 19.1.10; 19.2.9; 19.3.1
Next.js >=16.0.0 <= 16.4.0 16.4.1

Exploitation evidence

Exploitation not established. A public lab proof of concept exists (Hash Security, 17 October 2026). No in-the-wild exploitation was established in reviewed sources as of 12 November 2026.

Sources: React, Next.js / Vercel, Next.js / Vercel, Hash Security

Actions

  1. Take a controlled backup or confirm a recoverable build before updating.
  2. Update Next.js 16 to 16.4.1 or newer; for Next.js 15.5, move to 15.5.28 or a newer patched release as the official post recommends.
  3. Next.js ships compiled RSC, so updating React alone is insufficient; on other frameworks, update the actual react-server-dom packages or a framework release containing them, then rebuild and redeploy.
  4. Verify the deployed artifact, not just the lockfile, and test cached pages and Server Actions.
  5. No workaround is known for affected Next.js apps; update even if no similar function is identified.

Unknowns

  • Specific application configuration, any historical compromise, and the earliest real-world abuse.
  • The Next.js advisory GHSA-673q-mjm6-r5xr still carries no CVE as of 12 November 2026, so scanners matching on CVE alone may miss the Next.js side.
  • KEV absence cannot prove it was unexploited; the React CVE was only published by the CNA on 10 November 2026.

Sources

  • React · published · updated · retrieved https://github.com/react/react/security/advisories/GHSA-xqc2-xf4c-x3h3
  • Next.js / Vercel · published · updated · retrieved https://github.com/vercel/next.js/security/advisories/GHSA-673q-mjm6-r5xr
  • Next.js / Vercel · retrieved https://nextjs.org/blog/nextjs-security-update-october-14-2026
  • Hash Security · retrieved https://hash-sec.com/blog/the-use-cache-rce-how-a-typed-array-bug-in-nextjs-became-remote-code-execution
  • GitHub CNA / CVE Program · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-126187
  • GitHub Advisory Database · retrieved https://api.github.com/advisories/GHSA-xqc2-xf4c-x3h3

Change history

  1. — Published: New 10 November 2026 entry derived from 14 October 2026 originals; not a new incident.
  2. — Correction: Correction, 12 November 2026: the React advisory GHSA-xqc2-xf4c-x3h3 now carries CVE-2026-126187, published by the GitHub CNA on 10 November 2026, and appears in GitHub's global advisory database. Removed the earlier statements that no CVE was assigned and that global listing was unknown. Affected ranges, prerequisites, fixed versions and the 14 October 2026 advisory dates are unchanged.

Subscribe: RSS feed · JSON Feed · Feed format and fields