Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA GitHub_M

CVE-2026-126187: React: Unauthenticated Remote Code Execution in React Server Components

CriticalCVSS 9.5 · v4.0—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 39/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 78.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: react-server-dom-parcel (npm) 19.0.9, 19.1.10, 19.2.9; react-server-dom-turbopack (npm) 19.0.9, 19.1.10, 19.2.9; react-server-dom-webpack (npm) 19.0.9, 19.1.10, 19.2.9.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to react-server-dom-parcel (npm) 19.0.9, 19.1.10, 19.2.9; react-server-dom-turbopack (npm) 19.0.9, 19.1.10, 19.2.9; react-server-dom-webpack (npm) 19.0.9, 19.1.10, 19.2.9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

React is a JavaScript library for building user interfaces. From 19.0.0 until 19.0.9, 19.1.10, 19.2.9, and 19.3.1, the react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack packages are vulnerable to unauthenticated remote code execution through crafted payloads targeting frameworks that support React Server Components. The vulnerability only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value. Applications whose React code does not use a server are not affected. Applications that do not use a framework, bundler, or bundler plugin that supports React Server Components are not affected. This issue is fixed in versions 19.0.9, 19.1.10, 19.2.9, and 19.3.1.

Published
Nov 10, 2026
Updated
Nov 12, 2026
EPSS
1.7% · 78th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
38 / 40 · 9.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.7%

CNA vs NVD score

NVD
—
CNA · GitHub_M
9.5
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-126187

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for react records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • react react

    • >= 19.0.0, < 19.0.9, >= 19.1.0, < 19.1.10, >= 19.2.0, < 19.2.9, >= 19.3.0, < 19.3.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmreact-server-dom-parcelfrom 19.0.0 · before 19.0.919.0.9
npmreact-server-dom-parcelfrom 19.1.0 · before 19.1.1019.1.10
npmreact-server-dom-parcelfrom 19.2.0 · before 19.2.919.2.9
npmreact-server-dom-parcelfrom 19.3.0 · before 19.3.119.3.1
npmreact-server-dom-turbopackfrom 19.0.0 · before 19.0.919.0.9
npmreact-server-dom-turbopackfrom 19.1.0 · before 19.1.1019.1.10
npmreact-server-dom-turbopackfrom 19.2.0 · before 19.2.919.2.9
npmreact-server-dom-turbopackfrom 19.3.0 · before 19.3.119.3.1
npmreact-server-dom-webpackfrom 19.0.0 · before 19.0.919.0.9
npmreact-server-dom-webpackfrom 19.1.0 · before 19.1.1019.1.10
npmreact-server-dom-webpackfrom 19.2.0 · before 19.2.919.2.9
npmreact-server-dom-webpackfrom 19.3.0 · before 19.3.119.3.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:react-server-dom-parcel19.0.9Package registry (OSV)
npm:react-server-dom-parcel19.1.10Package registry (OSV)
npm:react-server-dom-parcel19.2.9Package registry (OSV)
npm:react-server-dom-parcel19.3.1Package registry (OSV)
npm:react-server-dom-turbopack19.0.9Package registry (OSV)
npm:react-server-dom-turbopack19.1.10Package registry (OSV)
npm:react-server-dom-turbopack19.2.9Package registry (OSV)
npm:react-server-dom-turbopack19.3.1Package registry (OSV)
npm:react-server-dom-webpack19.0.9Package registry (OSV)
npm:react-server-dom-webpack19.1.10Package registry (OSV)
npm:react-server-dom-webpack19.2.9Package registry (OSV)
npm:react-server-dom-webpack19.3.1Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub3 repositories2026-11-08 → 2026-11-12

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-3 d
  2. Published
  3. Fix recordedsame day
  4. TodayNov 13, 2026+3 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-502 · Deserialization of Untrusted Data

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

The bug in code

The whole CWE-502 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig):    raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Exploit maturitynone → poc
  2. Exploit maturity— → none
  3. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (14 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records