P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

React advisory says unauthenticated RCE and 'extremely rare'; fixed releases came 27 days earlier

The React project's advisory of 10 November 2026 calls CVE-2026-126187 unauthenticated remote code execution and says it only affects 'extremely rare cases'. The four fixed releases were published on 14 October, 27 days 5 hours earlier (derived); no saved page says why the advisory followed.

By · LinkedIn · · 20 min read

27 days 5 hours 38 minutes from the fixed releases to the advisory, and what that span does not show

The React project published four releases on Wednesday 14 October 2026, between 17:05:59 and 17:06:15 UTC: 19.0.9, 19.1.10, 19.2.9 and 19.3.1. Each release body is one line, "Improve transport protocol", under the heading React Server Components. The GitHub advisory GHSA-xqc2-xf4c-x3h3, for CVE-2026-126187, was published on Tuesday 10 November 2026 at 22:44:12 UTC; the CVE.org record is stamped 22:33:57 UTC, 10 minutes 15 seconds earlier (derived). The span from the first release to the advisory is 27 days 5 hours 38 minutes (derived: 14 October 17:05:59 to 10 November 22:44:12 UTC is 27 days 5 hours 38 minutes 13 seconds, or 653 hours). The advisory lists all four release tags among its references and says its fixes were back ported to those versions, so the advisory itself ties the October releases to the November record.

What the span does not establish. It runs from a release to a write-up. It does not show that anyone knew of the flaw on 14 October, that the releases were published to fix it, that anyone used the gap, or that the maintainers delayed anything. The four saved release bodies do not mention a vulnerability, and no saved page says why the advisory followed on 10 November. This briefing draws no verdict on how the fix was handled; it prints what the release notes say and what the advisory's own references say, and leaves the reason open.

The advisory is titled "React: Unauthenticated Remote Code Execution in React Server Components", carries the severity critical, and in its Impact text says that crafted payloads "can lead to remote code execution" and then that the flaw "only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value". The CVE.org record adds a CVSS 4.0 base score of 9.5. A CISA coordinator's stamp of 13 November reads Exploitation "none". NVD shows the status Deferred. This briefing sets the descriptions side by side and resolves nothing.

The advisory and the release notes are the React maintainers' own account of their own project: this is a statement by the party that wrote the code and the fix, and no independent analysis was read for this briefing. The advisory credits one finder and prints no name in the text this site read; the saved record carries an account handle, which this briefing does not repeat.

What the four release notes print

The four release records as saved on 15 Nov 2026. Times are the records' published_at stamps, in UTC. Source: the GitHub release records for the four fixed versions.

ReleasePublished (UTC)Body, under React Server Components
19.0.9 (October 14th, 2026)14 Oct, 17:05:59"Improve transport protocol", pull request 37842
19.1.10 (October 14th, 2026)14 Oct, 17:06:06"Improve transport protocol", pull request 37843
19.2.9 (October 14th, 2026)14 Oct, 17:06:10"Improve transport protocol", pull request 37844
19.3.1 (October 14th, 2026)14 Oct, 17:06:15"Improve transport protocol", pull request 37845

The four bodies have the same form: one bullet, the same words, a pull request number and two credited contributors. The words vulnerability, security and CVE appear in none of them (asserted against the saved records). The release drafts were created between 16:31 and 16:41 UTC on 14 October and published about half an hour later, within 16 seconds of one another (derived: 17:05:59 to 17:06:15).

Only one pull request record is saved, number 37844, which targets the 19.2.x release branch. Its title is "[19.2.x][Flight] Improve transport protocol"; it was opened at 15:48:44 UTC and merged at 16:32:37 UTC on 14 October (33 minutes 22 seconds before the first release was published, derived); its description is empty; and the record prints 5 commits, 1,583 additions, 252 deletions and 32 changed files. Those are the record's own counts. They say how large the change is, not what it changes, and the diff was not saved or read.

The advisory's references list five pull requests, 37842 to 37846, and five commits. The four release bodies name four of the pull requests, 37842 to 37845. Pull request 37846 is named by no saved release body, and what it is, or which branch it targets, is not stated by any saved page. What each of the five changes is not stated either: the diffs and commits were not read.

One detail may matter only to a reader following links. The release bodies link their pull requests under the facebook/react path; the advisory's references, and the saved pull request record, use react/react. The saved pages do not say whether one path forwards to the other.

Four descriptions of one flaw

The grid sets four things the saved records say about this flaw against what each leaves out. The title and the severity pull one way; the Impact sentence about "extremely rare cases" pulls another; the CVE.org vector and the CISA stamp are separate instruments again. None of the saved pages tries to reconcile them.

Drawn from the GitHub advisory record, the CVE.org record with its CISA-ADP container, as read on 15 November 2026. Amber marks wording that pulls in a different direction; red marks what no saved page says.

The severity. The GitHub record's severity field reads critical. Its older style cvss block is empty (vector and score both null) and its CVSS 3 block prints a score of 0.0 with no vector; its CVSS 4 block carries a vector and a score of 9.5. So the GitHub record does carry a CVSS score, in its CVSS 4 block, although a reader who looks only at the older blocks sees an empty block and a 0.0; this briefing reports each block as printed. The CVE.org record carries the same vector and the base score 9.5, labelled CRITICAL, in the container written by the CVE's assigner, GitHub_M. NVD copies the vector with the source security-advisories@github.com and the type Secondary, and shows no score of its own; its status is Deferred, which the saved page does not define.

The vector, metric by metric. The CVE.org record names these values: attack vector NETWORK, attack complexity LOW, attack requirements PRESENT, privileges required NONE, user interaction NONE; impact on the vulnerable system HIGH for confidentiality, integrity and availability; impact on subsequent systems HIGH for confidentiality and integrity and NONE for availability. The vector string is printed in the technical section below. This site did not recompute the 9.5, because the CVSS 4.0 calculation uses lookup tables that are not in the saved pages.

The one metric that touches the advisory's own wording is attack requirements. As general background, which the saved pages do not state and the specification of which was not read for this build, that metric records whether a successful attack depends on conditions of the target that the attacker does not control. Whether the advisory's rare conditions are what the vector means by PRESENT is not stated by any saved page, and this briefing does not say it is.

The CISA stamp. A container labelled CISA-ADP in the CVE record carries SSVC values: Exploitation "none", Automatable "no", Technical Impact "total", role CISA Coordinator, stamped 2026-11-13 at 16:44:19 UTC. NVD copies the same three values. They are a point in time: the saved pages give no reason for any value and no later stamp.

One more number. The GitHub record also carries an EPSS field printed as a percentage of 0.01763 and a percentile of 0.78333. The saved pages do not explain the model, give a date for the figures, or say what a reader should do with them, and the CVE.org and NVD records carry no such field.

Who prints what about severity and exploitation. Sources: the GitHub advisory record, the CVE.org record and the NVD record, as read on 15 Nov 2026.

PageWhat it printsWhat it leaves out
GitHub advisory, title and severityUnauthenticated Remote Code Execution; severity critical; CWE-502Any count of affected apps; any condition in the title.
GitHub advisory, Impact text"extremely rare cases" with multiple typed arrays and an attacker-controlled valueHow often; how an app can tell; any framework by name.
GitHub advisory, score blocksOld block empty; CVSS 3 block 0.0 with no vector; CVSS 4 block 9.5 with the vectorWhich block a tool should trust.
CVE.org record (assigner GitHub_M)CVSS 4.0, 9.5 CRITICAL, attack requirements PRESENT; CWE-502What PRESENT refers to.
NVD recordStatus Deferred; GitHub's vector as Secondary, 9.5A score of NVD's own.
CISA-ADP container, 13 NovSSVC: Exploitation none, Automatable no, Technical Impact totalThe reasons; any later update.
GitHub advisory, EPSS fieldPercentage 0.01763, percentile 0.78333Date, model, meaning.

Where the wording of the ranges and the records differs

Four saved texts give the affected and fixed versions: the advisory's prose, the advisory's machine readable ranges, the CVE.org record's description and its structured ranges. The ladder shows the version ranges the advisory prints. The prose and the structured ranges agree branch by branch; the differences below are in the writing, and each is reported as printed and not corrected.

Drawn from the advisory's Impact and Patches text, its machine readable ranges and the four release records, as read on 15 November 2026. The same ranges are printed for all three packages.

Differences between the saved texts, as printed. Sources: the GitHub advisory record, the CVE.org record, the NVD record and the four release records, as read on 15 Nov 2026.

ItemOne text saysAnother says
Fixed version for the 19.0 branchAdvisory patch line: "19.0.09"Advisory machine data, CVE.org record and release tag: 19.0.9
How the range is writtenAdvisory text: "19.0.0 through 19.0.8", then one range per branchCVE.org description: "From 19.0.0 until 19.0.9, 19.1.10, 19.2.9, and 19.3.1"; its structured data has one range per branch
Which package is namedAdvisory: three npm packages, react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopackCVE.org structured data: vendor react, product react; the three packages appear only in the description
The word unauthenticatedIn the advisory title and in the CVE.org descriptionNot in the advisory's Impact or Patches text
Who found itAdvisory credits one finder, type finderCVE.org record: discovery "UNKNOWN"
NVD publicationGitHub record as saved: the NVD published field is nullNVD record: published 10 Nov, 23:17:20.687, a time printed with no zone and read here as UTC

The typo is small and the machine data does not carry it: the advisory's own ranges, the CVE.org record and the release tag all say 19.0.9. A person following the prose could, though, search for a version that does not exist, and a script that parses the patch line would not find it (inference). The CVE.org description is harder to read literally: "From 19.0.0 until 19.0.9, 19.1.10, 19.2.9, and 19.3.1" could be taken as one run of versions from 19.0.0 to 19.3.1. The structured ranges next to it, and the advisory, say otherwise, and this briefing follows them; the prose of the CVE.org description is the only place the ambiguity sits.

The structured product in the CVE.org record is react, not the three packages the advisory names. A tool that matches on the product name would be looking at a package the advisory does not list; whether the react package itself is affected is not stated, and the advisory's only statement of scope is the three react-server-dom packages (inference about tooling, not a finding about the code). The saved pages also do not say which frameworks bundle those three packages: the advisory says only "frameworks supporting React Server Components" and names none.

The dates, in the order the saved records give them

Times are in UTC. The GitHub and CVE.org records print a Z; NVD prints times with no zone, which this site reads as UTC. The diagram runs from the merge of the only saved pull request to the state of the records on 15 November.

Dates from the GitHub release records, the pull request record, the GitHub advisory, the CVE.org record and the NVD record. Spans marked derived are this site's arithmetic.

Derived spans between dated points. Each end is read from a saved record; the arithmetic is this site's.

FromToSpan (derived)
Pull request 37844 merged, 14 Oct 16:32:37First release published, 14 Oct 17:05:5933 minutes 22 seconds
First release, 14 Oct 17:05:59Last release, 14 Oct 17:06:1516 seconds
First release, 14 Oct 17:05:59CVE.org record published, 10 Nov 22:33:5727 days 5 hours 27 minutes 58 seconds
First release, 14 Oct 17:05:59GitHub advisory published, 10 Nov 22:44:1227 days 5 hours 38 minutes 13 seconds
Last release, 14 Oct 17:06:15GitHub advisory published, 10 Nov 22:44:1227 days 5 hours 37 minutes 57 seconds
CVE ID reserved, 10 Nov 20:07:44CVE.org record published, 10 Nov 22:33:572 hours 26 minutes 13 seconds
CVE.org record published, 10 Nov 22:33:57GitHub advisory published, 10 Nov 22:44:1210 minutes 15 seconds
GitHub advisory published, 10 Nov 22:44:12NVD published, 10 Nov 23:17:20 (read as UTC)33 minutes 8 seconds
GitHub advisory published, 10 Nov 22:44:12CISA-ADP stamp, 13 Nov 16:44:192 days 18 hours 0 minutes 7 seconds
CISA-ADP stamp, 13 Nov 16:44:19CVE record updated, 13 Nov 16:45:0647 seconds
CVE record updated, 13 Nov 16:45:06NVD last modified, 13 Nov 17:17:25 (read as UTC)32 minutes 19 seconds
CISA-ADP stamp, 13 Nov 16:44:19Records saved, 15 Nov about 10:00about 1 day 17 hours

Two details are worth stating. First, the CVE.org record's last update, 13 November 16:45:06, matches to the millisecond the date of the CISA-ADP container inside it, while the container written by the assigner still carries its 10 November date; the later change therefore appears to be CISA's container (inference: the record does not say what changed). Second, the CVE ID was reserved at 20:07:44 UTC on 10 November, the same evening as the publication, so the record gives no sign of an earlier reservation; that says nothing about when the maintainers learned of the flaw, which the saved pages do not state.

What exploitation rests on

No saved page prints an exploitation report, a victim or an actor. The one statement about exploitation is the CISA-ADP stamp, and it reads "none". As read between 09:20 and 09:29 UTC on 15 November, the CISA Known Exploited Vulnerabilities catalog, version 2026.11.13, has no entry for this CVE. Both are facts at a time: the stamp is less than two days old when read, the catalog file is the one released on 13 November, and a reader should check both again before closing a ticket on the strength of either.

What each source says about exploitation. Sources: the CVE.org record, the NVD record, the GitHub advisory record and the release records, as read on 15 Nov 2026; the catalog line rests on the note made at the time.

SourceWhat it saysWhat it leaves out
CISA-ADP container, 13 Nov 16:44Exploitation "none", Automatable "no"The reasons; any later stamp.
CISA KEV catalog, version 2026.11.13No entry for this CVE when read on 15 NovAnything after that catalog release; the file is not saved.
GitHub advisoryNo claim of attackAny report, victim, actor or date.
CVE.org and NVD recordsNo claim of attack; NVD adds no KEV fieldsAny analysis of NVD's own; status Deferred.
Release notesDo not mention a vulnerabilityAnything about use of the flaw.

None of this says the flaw has not been used. Automatable "no" and Exploitation "none" are a coordinator's judgement on 13 November, with no evidence shown, and the saved pages cannot let a reader audit either. The narrower statement the pages allow is this: no saved page reports exploitation, the CISA stamp read none on 13 November, and the catalog did not list it on the morning of 15 November.

Labels that do the work of a control

"Extremely rare". The phrase is a frequency claim with no number, no test and no named framework behind it. It tells a reader how often the maintainers think the condition occurs; it does not tell an app owner whether this app is one of them. The advisory's own sentence is conditional on "multiple typed arrays and an attacker-controlled value", and the saved pages do not say how an owner would check an app for that.

"Critical" and "unauthenticated". The title and the 9.5 give the strongest label a scoring system has. They say nothing about how many apps are exposed, and the vector's own attack requirements metric reads PRESENT. A label that says critical and a sentence that says extremely rare are both on the same page, and a risk register that takes only one of them will mislead in one direction or the other.

"Not affected". The advisory says "If an app’s React code does not use a server, the app is not affected by this vulnerability." That is a statement an app owner can check, but it depends on knowing whether a framework, bundler or plugin in the build supports React Server Components, and the advisory names none.

"Updating immediately is recommended". The advisory says "Updating immediately is recommended." The four fixed versions have existed since 14 October, so a build whose lockfile has moved to one of them since then may already have followed the instruction without anyone calling it a security fix; whether a given lockfile has is for that lockfile to say.

What the records state, and what they do not

What is stated on a saved page and what is not, topic by topic. Sources: all saved records, read 15 Nov 2026.

TopicStated on a saved pageNot stated
Affected versionsThree 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.0Which frameworks bundle them, and at which framework versions.
Fixed versions19.0.9, 19.1.10, 19.2.9 and 19.3.1, published 14 OctWhy the advisory followed on 10 Nov.
Scope"extremely rare cases" with multiple typed arrays and an attacker-controlled valueWhat those cases are in practice; how an app can tell.
SeverityCritical; CVSS 4.0 9.5; CWE-502What attack requirements PRESENT refers to.
ExploitationCISA-ADP stamp 13 Nov: none; not in the KEV catalog on 15 Nov morningAny report; whether the stamp changed after 13 Nov.
The finderOne credited finder in the GitHub recordWhat was reported, and when; the CVE.org record says discovery UNKNOWN.
The changesFive pull requests and five commits listed as referencesWhat each changes; the diffs were not read.
FrameworksThe phrase frameworks supporting React Server ComponentsAny framework's own notice; none was read.
DetectionNothingAny log line, indicator or hunting query.

The version ranges and the scope sentences, as the records print them

The advisory prints affected and fixed versions, three package names and two sentences about when an app is not affected. They are copied exactly below from the saved GitHub advisory record and the CVE.org record, read on 15 November 2026. This site ran none of it and adds nothing: the saved pages publish no payload, no indicator, no log line, no detection rule and no command for finding the versions, and none is invented here. Copy from the advisory itself where you can.

The affected versions and packages. The advisory's Impact text lists them as follows. Read each version as a range within one branch: 19.3.0 is the only affected 19.3 release.

Text
The vulnerability exists in versions 19.0.0 through 19.0.8, 19.1.0 through 19.1.9, 19.2.0 through 19.2.8 and 19.3.0 of:
- react-server-dom-webpack
- react-server-dom-parcel
- react-server-dom-turbopack
The advisory's Impact text on versions and packages, as printed in the GitHub advisory record, read 15 November 2026.

The machine readable ranges. The advisory record prints the same four ranges for each of the three packages, with a first patched version for each.

The ranges printed for each of the three packages. Source: the GitHub advisory record, vulnerabilities list, read 15 Nov 2026.

Affected rangeFirst patched versionPackage names
>= 19.0.0, < 19.0.919.0.9react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack
>= 19.1.0, < 19.1.1019.1.10react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack
>= 19.2.0, < 19.2.919.2.9react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack
>= 19.3.0, < 19.3.119.3.1react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack

The patch line. The first line contains the 19.0.09 in the advisory's text; the machine data says 19.0.9.

Text
Fixes were back ported to versions 19.0.09, 19.1.10, 19.2.9, and 19.3.1.
If applications are using any of the above packages please upgrade to any of the fixed versions immediately.
The advisory's Patches text, as printed in the GitHub advisory record, read 15 November 2026.

When an app is not affected. These are the advisory's two sentences, which an owner can check against a build.

Text
If an app’s React code does not use a server, the app is not affected by this vulnerability.
If an app does not use a framework, bundler, or bundler plugin that supports React Server Components, the app is not affected by this vulnerability.
The advisory's two not affected sentences, as printed in the GitHub advisory record, read 15 November 2026.

The CVE.org description. The first sentence is the CVE record's version wording, discussed above; it is one run of text with four version numbers.

Text
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 first sentence of the CVE.org record's description, as printed, read 15 November 2026.

The CVSS 4.0 vector. The CVE.org record prints it as follows, and the GitHub advisory record prints the same string. The metric values are listed in plain words in the section on the four descriptions.

Text
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 CVSS 4.0 vector string, as printed in the CVE.org record and the GitHub advisory record, read 15 November 2026.

What to do, in order

Take this with you

The advisory's steps first, then this site's suggestions

  • The advisory's own step: if an app uses react-server-dom-webpack, react-server-dom-parcel or react-server-dom-turbopack, upgrade to a fixed version immediately: 19.0.9, 19.1.10, 19.2.9 or 19.3.1.
  • The advisory's own scope: an app whose React code does not use a server is not affected, and neither is an app that uses no framework, bundler or bundler plugin supporting React Server Components.
  • This site's suggestion: find out whether your framework bundles one of the three packages. The advisory names no framework, so read the framework's own notice, which this site did not.
  • This site's suggestion: the four fixed versions were published on 14 October 2026, so a build updated since then may already carry one. Whether yours did is for your own lockfile to say. The advisory prints no command for finding the versions and this site adds none.
  • This site's suggestion: do not treat extremely rare as not you until the two checks above are done.
  • For risk teams: the advisory text and the severity label disagree on scope. Decide with your own inventory of what runs where, not with the label alone.
  • This site's suggestion: when you record the CVE in a scanner or register, key it on the three package names and the four ranges, not on the product name react, and check the 19.0.9 fix version by hand because the advisory's prose prints 19.0.09.
  • This site's suggestion: re-check the CISA stamp and the Known Exploited Vulnerabilities catalog before closing a ticket. The stamp read none on 13 November and the catalog had no entry on the morning of 15 November; both can change.

The question the records leave open

The advisory calls it unauthenticated remote code execution and critical, then says it only affects extremely rare cases, and the fixed releases are 27 days older than the advisory, so who will say how rare, for which frameworks, and why the write-up came when it did?

Key facts

Sources

  1. PrimaryGitHub advisory GHSA-xqc2-xf4c-x3h3, API record: title, severity, Impact and Patches text, machine readable ranges, score blocks, CWE-502, references (five pull requests, five commits, four release tags), credits, EPSS field. Published 10 November 2026 22:44:12 UTC. Saved by the lead on 15 November 2026GitHub (React project advisory)accessed 2026-11-15
  2. PrimaryCVE record CVE-2026-126187 (CVE 5.2 JSON): description, structured ranges, CVSS 4.0 vector and score 9.5, CWE-502, and the CISA-ADP container with the SSVC values. Published 10 November 2026 22:33:57 UTC, updated 13 November 16:45:06 UTC. Saved by the lead on 15 November 2026CVE Program (cveawg.mitre.org)accessed 2026-11-15
  3. PrimaryNVD record CVE-2026-126187 (API 2.0): status Deferred, GitHub's vector as a Secondary metric, the CISA SSVC copy, no score of its own. Last modified 13 November 2026 17:17 UTC. Saved by the lead on 15 November 2026NIST National Vulnerability Databaseaccessed 2026-11-15
  4. PrimaryRelease 19.0.9, published 14 October 2026 at 17:05:59 UTC: the release record, whose body reads Improve transport protocol under React Server Components. Saved by the lead on 15 November 2026GitHub (React project release)accessed 2026-11-15
  5. PrimaryRelease 19.1.10, published 14 October 2026 at 17:06:06 UTC: the release record, whose body reads Improve transport protocol under React Server Components. Saved by the lead on 15 November 2026GitHub (React project release)accessed 2026-11-15
  6. PrimaryRelease 19.2.9, published 14 October 2026 at 17:06:10 UTC: the release record, whose body reads Improve transport protocol under React Server Components. Saved by the lead on 15 November 2026GitHub (React project release)accessed 2026-11-15
  7. PrimaryRelease 19.3.1, published 14 October 2026 at 17:06:15 UTC: the release record, whose body reads Improve transport protocol under React Server Components. Saved by the lead on 15 November 2026GitHub (React project release)accessed 2026-11-15
  8. PrimaryPull request 37844 metadata only (title, dates, branch, counts); the diff was not saved or read. Saved by the lead on 15 November 2026GitHub (React project pull request)accessed 2026-11-15

Share this briefing

Know someone who owns this problem? Send it to them.

Related briefings

The briefing, in your inbox

Practitioner analysis of cyber and AI security news. No vendor noise.

How often

Every new briefing in one email, at 7am, or at 7am, 12:30pm and 6pm. Nothing is sent when nothing is new. Unsubscribe any time.