All CVEs

React Server Components typed-array RCE (CVE-2026-126187; Next.js GHSA-673q): unauthenticated attacker can call a Server Action with chosen arguments, but only in "extremely rare" apps: Next.js 16.0.0–16.4.0 with Cache Components and a use cache function returning several typed arrays (or react-server-dom-* 19.x elsewhere). Lab exploit public, no attacks, not in KEV. Fix: Next.js 16.4.1+ / react-server-dom-* 19.0.9, 19.1.10, 19.2.9, 19.3.1. Next.js 15.x not affected. https://tldrcve.com/react-typed-array-rce/

React (Next.js) · CVE-2026-126187

React RSC RCE

Patch now if…Only Next 16 apps returning typed arrays from use cache.

A bug in how React Server Components package several typed arrays (binary data) in one response can let an attacker with no login call one of the app's Server Actions with arguments they choose. React says it only affects "extremely rare cases"; in Next.js it needs Cache Components and a use cache function that returns several typed arrays. A lab exploit is public, no attacks are reported, and the fix has been out since 14 Oct; the CVE ID came on 10 Nov.

How scary is it?

updated 21 Nov
  • Yes: Works without logging in1,2
  • Yes: Public exploit code is out5
  • No: No attacks seen yet3,9
  • No: Not on CISA's exploited list8

Scare-o-meter

Keep an eye on it

Patch on schedule.
Watch for news.

Are you affected? only if all are true

1Next.js 16.0.0 – 16.4.0command

Or react-server-dom-webpack, -parcel or -turbopack 19.0.0–19.0.8, 19.1.0–19.1.9, 19.2.0–19.2.8 or 19.3.0 in another Server Components setup. Next.js 15.x isn't affected by this bug. Apps whose React code doesn't use a server aren't affected.1,2,7

npm ls next react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack
2Cache Components is oncommand

The App Router with Cache Components (cacheComponents: true in the Next.js config).2,6

grep -n cacheComponents next.config.*
3A use cache function returns typed arrayscommand

One that returns several typed arrays. Hash Security adds that they must be larger than 4 KB, share one buffer, and come with a value the attacker influences.2,4

grep -rln "use cache" app src
4A Server Action does something dangerous

Running commands needs a Server Action that does something risky with the arguments the attacker supplies, per Hash Security; their lab app wraps a shell command in one.4,5

What to do

1Upgradecommand

Next.js 16.4.1 or later (16.4.5 also fixes the Next.js image bug). Other setups: react-server-dom-* 19.0.9, 19.1.10, 19.2.9 or 19.3.1. Next.js says to upgrade even if your app has no such function.1,2

npm ls next
2No workaround

Next.js says there's no workaround for apps with an affected use cache function.2

This page shows you how to check. It can't tell you you're safe.

Sources (9) and changelog
  1. React GHSA-xqc2: affected and fixed react-server-dom versions, 'extremely rare' 14 Oct
  2. Next.js GHSA-673q: Next 16.0.0–16.4.0, Cache Components, no workaround 14 Oct
  3. CVE record: CVE-2026-126187, CISA assessment exploitation none 10 Nov
  4. Hash Security: how the bug works, what a lab exploit needs 17 Oct
  5. Hash Security: public lab exploit 17 Oct
  6. Next.js docs: the cacheComponents setting
  7. Next.js: v15.5.28 release notes (no typed-array fix needed) 14 Oct
  8. CISA KEV catalog: not listed
  9. Cloudflare Zero Wire: no exploitation reported as of 11 Nov 11 Nov