Fix React Server Components RCE vulnerability#1142
Merged
Conversation
## React Flight / Next.js RCE Advisory - Security Patch ### Summary Updated the edge-runtime repository to address the React Flight / Next.js RCE vulnerability advisory. The project was identified as affected due to the use of Next.js in the `docs` workspace package. ### Analysis The repository is a monorepo using pnpm workspaces containing: - 13 packages in the `packages/` directory (core libraries for edge runtime functionality) - 1 documentation site in the `docs/` directory **Affected Component:** - `docs/package.json` - Contains Next.js 15.2.4 with React 18 **Not Affected:** - No workspace packages directly depend on Next.js - No packages use React Flight packages (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`) - React versions are 18.x (not vulnerable 19.x versions) ### Changes Made #### Modified: `docs/package.json` - Updated `next` from `~15.2.4` to `~15.2.6` - React and react-dom remain at version 18 (not affected by vulnerability) - Next.js 15.2.x patch rule: upgrade to 15.2.6 ✓ #### Modified: `pnpm-lock.yaml` - Updated lockfile to resolve Next.js 15.2.6 and its dependencies - Lockfile confirms Next.js 15.2.6 is now pinned with react@18.3.1 and react-dom@18.3.1 ### Verification - ✓ `pnpm install --no-frozen-lockfile` completed successfully - ✓ `next build` in docs/ completed successfully with no errors - ✓ All 20 pages generated and optimized correctly - ✓ No dependency conflicts or compatibility issues ### Why No Changes to React? According to the advisory, React 18.x is not vulnerable. The vulnerability affects React 19.0.0, 19.1.0, 19.1.1, and 19.2.0. Since this project uses React 18, no React version update is required. ### Notes - The root package.json contains `"next": "latest"` as a devDependency (for development/testing) - This only affects the docs workspace which has explicit version constraints - The security patch (Next.js 15.2.6) has been successfully applied and verified Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
|
Contributor
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A critical remote code execution (RCE) vulnerability in React Server Components, impacting frameworks such as Next.js, was identified in the project edge-runtime. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.
This issue is tracked under:
This automated pull request upgrades the affected React and Next.js packages to patched versions that remediate the issue.
More Info