CVEHit Business Advisory by IntegrityLab.ai
What’s the evidence?
Update the server-dom fix for your version group — CVE-2026-126187: Business Triage
The reported finding
- Required conditions
- An affected version of any one of these packages is deployed:
- react-server-dom-webpack
- react-server-dom-parcel
- react-server-dom-turbopack
- React Server Components support comes from any one of:
- A framework
- A bundler
- A bundler plugin
- The React code uses a server.
- An attacker can reach that processing.
- The GitHub advisory says crafted payloads aimed at those frameworks can lead to remote code execution.
- The CVE description says this only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value.
- The vendor says applications whose React code does not use a server are not affected.
- The vendor says applications are not affected when they do not use any of these with React Server Components support:
- A framework
- A bundler
- A bundler plugin
- Reported outcome
- The advisory title and the CVE title call this unauthenticated remote code execution.
- CWE-502 is deserialization of untrusted data. The packages process response data that an attacker can influence.
- The CVE record reports:
- CVSS 4.0 base score: 9.5
- Severity: Critical
- 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
- The GitHub advisory reports:
- Base score: 9.5
- Severity: Critical
- The same vector string
- AT:P means attack requirements are present. The advisory text states the rare response case. The score does not remove that case.
- The vector sets:
- Privileges required: none
- User interaction: none
- The vector sets:
- Subsequent confidentiality: high
- Subsequent integrity: high
- Subsequent availability: none
Those ratings are not evidence that another system was reached.
- These sources do not report observed exploitation.
Fix guidance
- GitHub advisory GHSA-xqc2-xf4c-x3h3 recommends updating immediately when these packages are in use.
- Install the fixed release for the group you run. The advisory also says a listed fixed version is a fix. These sources do not require every app to move to 19.3.1.
- These sources do not say which group is most common.
- The advisory package tables and the CVE record agree on the fixed releases.
- The advisory Patches sentence says 19.0.09. Use 19.0.9.
- The CVE affected product name is react. The description and the advisory limit the flaw to:
- react-server-dom-webpack
- react-server-dom-parcel
- react-server-dom-turbopack
- The named affected ranges start at 19.0.0. These sources do not name releases before 19.0.0 as affected.
- The vendor says an app is not affected when its React code does not use a server.
- The vendor says an app is not affected when it does not use any of these with React Server Components support:
- A framework
- A bundler
- A bundler plugin
- The GitHub advisory page displays October 14, 2026.
- Release tag v19.0.9 is dated October 14, 2026.
- These retrieved sources do not date:
- The CVE record was published on November 10, 2026 at 22:33:57.528 UTC.
- That CVE time is not the first public disclosure. The advisory page displays October 14, 2026.
- These sources do not state an attack start date.
- KEV catalog 2026.11.13, released November 13, 2026 at 20:24:18 UTC, was checked at 21:35 UTC.
- That catalog has no entry for CVE-2026-126187.
- CISA assessment in the CVE record, dated November 13, 2026 at 16:44 UTC (SSVC 2.0.3):
- Exploitation: none.
- Automatable: no.
- Technical Impact: total.
- A missing KEV entry leaves exploitation unknown.
- Exploitation: none means CISA had no evidence of exploitation in that assessment. It does not prove no attacks occurred or that your systems are safe.
- When an affected version was deployed before the update, include that period in the harm review. The completed update leaves that earlier harm question open.
What IntegrityLab.ai can check
- The reviewed unauthenticated HTTP check can record:
- A reachable web service
- The server name returned in a response
- That result is a clue for an administrator.
- It does not prove:
- The installed product
- The package
- The version
- The security patch
- The vulnerable configuration
- Compromise
- An absent identifying response leaves the product question open.
- A front server can hide the service behind it.
- No validated detection check for CVE-2026-126187 was established.
- This review cannot confirm:
- React Server Components use
- A server-dom package
- The required response contents
- Provider inventory
- Hosted-service inventory
- The Application owner has to establish those facts from internal records.
- When a Provider builds or hosts the app, the Provider's inventory is the record.
- The reviewed discovery code records:
- HTTP status
- Page title
- Content length
- Server header
- The reviewed scanner data, including nuclei data, contained no reference to CVE-2026-126187.
- This review covers the inspected code and data only.
Sources and vendor guidance
← Back to article questions