Contact us
← Article questionsWhat should we do?

CVEHit Business Advisory by IntegrityLab.ai

What should we do?

Update the server-dom fix for your version group — CVE-2026-126187: Business Triage

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.

← Back to article questions

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…