Contact us
← CVEHit Business AdvisoryReact Server Components CVE-2026-126187: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published

Update the server-dom fix for your version group — CVE-2026-126187: Business Triage9.5/10Critical · CVSS 4.0GitHubFix availableBy version groupCISA assessmentCVE.org sourceNo KEVChecked Nov 13

Confirm the deployed server-dom package and install the fixed release for that version group. Research: CVE record and KEV checked November 13, 2026.

Check these three things.

React Server Components prepare part of the interface on a server, using packages whose names start with react-server-dom. Confirm the installed fix, whether an attacker can reach that server, and whether your records show harm.

  1. Application owner: confirm the installed server-dom version group and its fixed release. A 19.3.0 install needs 19.3.1. Each other group has its own fix.
    What to confirm
    • These releases belong to version groups named by their first two numbers. For example, 19.0.8 is in the 19.0 group.
    • The CVE description and the GitHub advisory name these packages:
      • react-server-dom-webpack
      • react-server-dom-parcel
      • react-server-dom-turbopack
    • The CVE product field says react. A React interface without one of those packages is outside this flaw.
    • Each version group has its own fixed release. The vendor recommends updating affected packages immediately.
    • The CVE record lists each group as affected from its start version up to but not including the fix.
    • The advisory Patches sentence says 19.0.09. Use 19.0.9. The package tables, the CVE record, and release tag v19.0.9 say 19.0.9.
    • The advisory says a listed fixed version on any of these lines 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.
    • If no package record is available, the fix status stays unresolved.
    • An affected package you deploy needs its group fix even when the rare response case is unconfirmed.
    • Record:
      • Package name
      • Installed version
      • Source of that version
      • Date checked
  2. Application owner: check whether an attacker can reach the vendor's rare response case.
    When the risk applies
    • The GitHub advisory says this only affects extremely rare cases where both are true:
      • Responses transport multiple typed arrays. A typed array is a block of binary data.
      • An attacker-controlled value is included.
    • An affected package that is in use needs its group fix even when this case is unconfirmed.
    • The vendor says the app is not affected when its React code does not use a server.
    • The vendor says the app is not affected when it does not use any of these with React Server Components support:
      • A framework
      • A bundler
      • A bundler plugin
    • React's Server Components documentation says they can run:
      • Once at build time on a CI server
      • On each request on a web server
    • The documentation says a web server is not required for build-time use.
    • The documentation treats that build environment as a server. Build-time use is not, by itself, the vendor's not-affected case.
    • The Server Components name does not show that a server is open to the internet.
    • The CVE record and the GitHub advisory require:
      • No privileges
      • No user interaction
    • Both sources set attack requirements to present. The advisory text states the rare response case.
    • Frontend React use leaves the package question unresolved.
    • Records:
      • Whether a server-dom package is in the deployed build
      • Whether React Server Components support comes from any one of:
        • A framework
        • A bundler
        • A bundler plugin
      • Whether React code uses a server
      • Whether an attacker can reach that processing
      • Source of each record
      • Date checked
  3. Security owner: review retained records for unauthorized activity and service interruption.
    What the records can show
    • Unexpected code run by the application
    • Unexpected access to data the application can read
    • Unexpected changes to application content or records
    • Unexpected connections started by the application
    • Interruption in application logs or uptime alerts
    • Access to another system requires more than a network connection.
    • An interruption leaves the break-in question unresolved.
    • A gap in the records leaves harm unresolved.
    • Shown unauthorized activity needs a response even when this CVE is not established as the cause.
    • A missing KEV entry leaves exploitation unknown.
    • CISA’s assessment does not establish whether your systems were attacked.
    • These sources do not publish an indicator for this CVE.

If an affected server-dom package is in use, update it to that group's fix even when the rare response case is unconfirmed. Review retained records for harm. A completed update leaves the question of earlier harm open.

Do Now

  • System owner: update each affected server-dom package you deploy to the fixed release for its group. A 19.3.0 install needs 19.3.1. Each other group has its own fix. Do not wait for proof of the rare response case.
    Proof the update is done
    • Versions belong to groups named by their first two numbers. For example, 19.0.8 is in the 19.0 group.
    • Install the fix for the group you run:
      Fixed release for each version group
      Version groupAdvisory affected releasesCVE record rangeFixed release
      19.019.0.0 through 19.0.819.0.0 up to but not including 19.0.919.0.9
      19.119.1.0 through 19.1.919.1.0 up to but not including 19.1.1019.1.10
      19.219.2.0 through 19.2.819.2.0 up to but not including 19.2.919.2.9
      19.319.3.019.3.0 up to but not including 19.3.119.3.1
    • The advisory Patches sentence says 19.0.09. Install 19.0.9.
    • The advisory says you may update to any listed fixed version. These sources do not require every app to move to 19.3.1.
    • If the version group is missing from authorized records, the fix choice stays unresolved.
    • Do not default an unknown group to 19.3.1.
    • The vendor recommends an immediate update when these packages are in use.
    • After the update, record:
      • Package name
      • Installed version
      • Source of that record
      • Date checked
    • When a Provider applies the fix, obtain the Provider's statement naming:
      • The package
      • The deployed version
      • The date of the statement
  • Application owner: establish whether the affected server processing is reachable.
    Records that show exposure
    • Use authorized records:
      • Either package record:
        • The dependency lockfile
        • The deployed bill of materials
      • Which of these includes the package:
        • The framework
        • The bundler
        • The bundler plugin
      • The Provider's inventory, when a Provider builds or hosts the app
    • Frontend React use leaves the package question unresolved.
    • The vendor says the app is not affected when its React code does not use a server.
    • The vendor says the app is not affected when it does not use any of these with React Server Components support:
      • A framework
      • A bundler
      • A bundler plugin
    • Build-time Server Components still use a server environment in the React documentation. Treat that as server use unless records show a vendor not-affected condition.
    • The Server Components name leaves internet reachability unresolved.
    • The vendor calls this extremely rare. The rare case requires both:
      • Responses transport multiple typed arrays.
      • An attacker-controlled value is included.
    • No attacker sign-in is required.
    • No user click is required.
    • Record:
      • Package name
      • Installed version
      • Whether React code uses a server
      • Whether an attacker can reach that processing
      • Source of each record
      • Date checked
  • Security owner: review retained application and host records for unauthorized activity.
    Where to look first
    • Include deployments that ran an affected package, including deployments already updated.
    • Review retained records for:
      • Unexpected code run by the application
      • Unexpected access to data the application can read
      • Unexpected changes to application content or records
      • Unexpected connections started by the application
      • Service interruptions already in logs or uptime alerts
    • Access to another system requires more than a network connection.
    • An interruption leaves the break-in question unresolved.
    • If the records show a break-in, start response now.
    • Act on signs of unauthorized activity even when this CVE cannot be shown as the cause.
    • These sources do not publish an indicator for this CVE.
    • A gap in the records leaves the harm question unresolved.
    • A missing KEV entry leaves exploitation unknown.
    • CISA’s assessment does not establish whether your systems were attacked.
    • Record:
      • Records reviewed
      • Period covered
      • Source of the records
      • Date reviewed
      • Whether unauthorized activity was shown

Do Next

  • Operations owner: watch application logs and uptime alerts for interruption until every affected update is confirmed.
    When to escalate
    • If interruption stops customer or staff work, handle it as a service incident now.
    • Do not wait to prove this flaw caused it.
    • An interruption leaves the break-in question unresolved.
    • Send signs of unauthorized access to the Security owner.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

The reported finding

Unauthenticated remote code execution

Original advisory →
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:
    • v19.1.10
    • v19.2.9
    • v19.3.1
  • 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.

How to read the score

GitHub CVSS 4.0: 9.5 (Critical). Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

Need an independent review of your public exposure?

See IntegrityLab.ai →

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…