Taiwan Information Security Association

Security alertsSat, 14 Nov 2026

React Server Components vulnerability: check server dependencies and deploy the fixes

CVE-2026-126187 can allow unauthenticated remote code execution in rare React Server Components response scenarios. Check the dependencies in running builds, apply the React or Next.js update and verify the redeployment.

01

Article

If you run React Server Components in a production website or service, check the server dependencies in the deployed build. React and Next.js rate CVE-2026-126187 at CVSS v4.0 9.5. The CVE Program record was published on 10 November 2026 UTC.

React describes an extremely rare condition. The server response has to carry more than one typed array together with a value the attacker controls. If that condition is present, crafted input may lead to remote code execution without signing in. React says applications without server-side React code, or without a framework, bundler or bundler plugin supporting React Server Components, are outside the affected scope.

In an enterprise deployment, assess what the server process can access, including application secrets, internal APIs, databases and storage. Treat those as possible downstream consequences according to the service’s actual permissions. CISA’s 13 November SSVC assessment recorded no known exploitation.

Attack flowHow a rare response condition can lead to code execution
  1. 01

    Reach an affected server-side route

    The deployment uses an affected React Server Components package through a supporting framework or build integration.

  2. 02

    Meet the response condition

    The response carries multiple typed arrays and a value controlled by the attacker.

  3. 03

    Trigger the vulnerable handling

    Crafted input may trigger the issue without an account.

  4. 04

    Reach resources available to the process

    Code may run with the server process’s access to files, secrets or connected services.

Affected packages, versions and fixes

React lists the same affected and fixed ranges for react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack.

Affected releasesFixed release
19.0.0 through 19.0.819.0.9
19.1.0 through 19.1.919.1.10
19.2.0 through 19.2.819.2.9
19.3.019.3.1

Next.js lists 16.0.0 through 16.4.0. Its advisory identifies applications using both the App Router and Cache Components, with a use cache function that returns multiple typed arrays. Upgrade to 16.4.1 or a supported later fixed release. Next.js recommends updating immediately even if you have no such function. The vendor has no known workaround for applications that meet these conditions.

Response flowRecommended actions: from the perimeter to core systems
  1. 01

    Inventory dependencies and running deployments

    Check dependency lockfiles and installed versions in production, staging, standby and outsourced deployments. Include framework-managed and bundled copies in container or serverless images.

    See what to doResources: 1

    TWISA member solutions

    Inventory dependencies and running deployments

    Use exposure and vulnerability management to match reachable application routes to the packages their deployed artifacts actually contain.

  2. 02

    Update and redeploy

    Apply the React package or framework update for the affected branch. Rebuild and roll out the clean artifacts, then check the running version across replicas and environments.

    View guidanceResources: 2

    Response guidance

    Update and redeploy

    Apply the React package or framework update for the affected branch. Rebuild and roll out the clean artifacts, then check the running version across replicas and environments.

  3. 03

    Retest the patched application

    In an authorized test environment, verify the deployed version and exercise relevant server routes, including cache behavior, data responses and business functions.

    See what to doResources: 1

    TWISA member solutions

    Retest the patched application

    Use application and API security testing to check the updated application and its request and response boundaries.

  4. 04

    Limit what the application can reach

    Review service accounts, database grants, API scopes, secrets and outbound access. Give the server process only the permissions it needs and segment access to internal systems.

    See what to doResources: 2

    TWISA member solutions

    Limit what the application can reach

    Review service identity privileges and enforce network boundaries around databases, internal APIs and secret stores.

  5. 05

    Investigate anomalies and verify recovery

    Preserve and correlate edge, application, container, host and identity records. Review unusual process launches, outbound requests and service account use. If you find evidence of compromise, isolate affected workloads, scope reachable systems and data, rotate exposed credentials where warranted and restore from trusted artifacts.

    See what to doResources: 2

    TWISA member solutions

    Investigate anomalies and verify recovery

    Use monitoring to correlate events across the application stack and incident response services to preserve evidence, determine impact and validate recovery.

Response flowProactive testing and retesting
  1. 01

    Find reachable assets and scan dependencies

    Check externally and internally reachable applications, APIs and their actual framework and dependency versions.

  2. 02

    Exercise the application under authorization

    Use penetration testing, API tests and attack simulation in a controlled environment to validate relevant server routes.

  3. 03

    Verify what happens at the edge and origin

    If a WAF fronts the route, check the request, alert, actual block and backend result individually. Apply the vendor update to fix the vulnerable dependency.

  4. 04

    Confirm behavior after the update

    Retest business functions and the deployed version. Check host privilege boundaries and internal reachability separately from web requests.

Defense architectureProtect the web entry point, application runtime and connected data

Map in-house and outsourced applications, framework-managed dependencies, build artifacts and container images.

Allow authorized traffic and apply controls at each layer.

  1. 01

    Web and API entry

    Public and internal application routes

    Limit exposureRemove unnecessary routes and monitor unusual requests.

  2. 02

    React application runtime

    Framework, server packages and deployed artifacts

    Patch and verifyUpdate direct and transitive dependencies, rebuild and verify running instances.

  3. 03

    Internal services and data

    Service identities, APIs, databases and secrets

    Limit impactUse least privilege, network segmentation and tested backups.

Feed logs and traffic data from each layer into monitoring and response.

  1. Monitor, investigate and recoverCorrelate web, application, container, host and identity records. Preserve evidence and verify recovery from trusted artifacts.

Inventory personal and sensitive data the service can reach. Apply encryption or masking where appropriate, review which identities can retrieve plaintext, and test restoration from backups.

TWISA member solutions

Official sources

For further product and service details, please contact the relevant TWISA members.

Advisory updated: 2026/11/14. Check the vendor’s latest information for product support and fixes.