Skip to content

Update dependency react-server-dom-webpack to v19.3.1 [SECURITY] - #906

Open
devdogs-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-react-server-dom-webpack-vulnerability
Open

devdogs-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-react-server-dom-webpack-vulnerability

Conversation

@devdogs-renovate

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
react-server-dom-webpack (source) 19.3.0 → 19.3.1 age confidence

React: Unauthenticated Remote Code Execution in React Server Components

CVE-2026-126187 / GHSA-xqc2-xf4c-x3h3

More information

Details

Impact

Crafted payloads targeting frameworks supporting React Server Components can lead to remote code execution. This only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value.

Updating immediately is recommended.

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
Patches

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.

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.

Severity

  • CVSS Score: 9.5 / 10 (Critical)
  • Vector String: 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

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


React: Unauthenticated Remote Code Execution in React Server Components

CVE-2026-126187 / GHSA-xqc2-xf4c-x3h3

More information

Details

Impact

Crafted payloads targeting frameworks supporting React Server Components can lead to remote code execution. This only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value.

Updating immediately is recommended.

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
Patches

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.

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.

Severity

  • CVSS Score: 9.5 / 10 (Critical)
  • Vector String: 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

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

react/react (react-server-dom-webpack)

v19.3.1: 19.3.1 (October 14th, 2026)

Compare Source

React Server Components


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@devdogs-renovate

Copy link
Copy Markdown
Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
? Verifying lockfile against supply-chain policies (923 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
[WARN] deprecated eslint@9.39.5: This version is no longer supported. Please see https://eslint.org/version-support for other options.
Progress: resolved 47, reused 0, downloaded 0, added 0
Progress: resolved 49, reused 0, downloaded 0, added 0
Progress: resolved 226, reused 0, downloaded 0, added 0
Progress: resolved 248, reused 0, downloaded 0, added 0
Progress: resolved 386, reused 0, downloaded 0, added 0
Progress: resolved 500, reused 0, downloaded 0, added 0
Progress: resolved 666, reused 0, downloaded 0, added 0
Progress: resolved 672, reused 0, downloaded 0, added 0
Progress: resolved 675, reused 0, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (923 entries in 10.1s)
Progress: resolved 780, reused 0, downloaded 0, added 0
[ERR_PNPM_UNUSED_PATCH] The following patches were not used: react-server-dom-webpack@19.3.0

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.
Progress: resolved 923, reused 0, downloaded 0, added 0

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants