Fix React Server Components RCE vulnerability#4
Draft
vercel[bot] wants to merge 1 commit intomasterfrom
Draft
Conversation
## React Flight / Next.js RCE Advisory Patch ### Summary Updated the project to address the React Flight / Next.js RCE advisory (CVE affecting Next.js and React Server Components). ### Vulnerability Detection The project was confirmed to be affected: - ✅ Uses **Next.js 15.2.1** (vulnerable version in 15.2.x range) - ✅ Does not use React Flight packages (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`) - ❌ Therefore, only Next.js upgrade is required ### Changes Made #### Modified Files: 1. **package.json** - Upgraded `next`: `^15.2.1` → `15.2.6` (patched version for 15.2.x) - React and React DOM were NOT modified (as per advisory - Next.js manages these internally) 2. **package-lock.json** - Updated by running `npm install` to reflect the patched Next.js version - Verified that lockfile resolves to `[email protected]` ### Verification Steps Completed ✅ **Dependency Installation**: Ran `npm install` successfully - 418 packages added ✅ **Version Verification**: Confirmed `[email protected]` is installed via `npm list next` ✅ **Build Verification**: Ran `npm run build` - Build succeeded with 0 errors ✅ **Linting**: Ran `npm run lint` - 0 ESLint warnings or errors ### Implementation Notes - The project is a single-package Next.js application (not a monorepo) - React and React-DOM versions (18.3.1) were NOT modified because Next.js 15.2.6 supplies the correct patched React dependency versions automatically - Used exact version pinning (`15.2.6`) instead of caret range to ensure the patched version is used - Build completed successfully with no dependency-related errors ### Advisory Details This patch addresses the React Flight / Next.js RCE vulnerability by upgrading to a patched Next.js version that includes security fixes for Server Component processing. The patched version ensures that malicious serialized data cannot be exploited through the React Flight protocol. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel 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
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.
Important
This is an automatic PR generated by Vercel to help you with patching efforts. We can't guarantee it's comprehensive, and it may contain mistakes. Please review our guidance before merging these changes.
A critical remote code execution (RCE) vulnerability in React Server Components, impacting frameworks such as Next.js, was identified in the project mcmaster-igem. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.
This issue is tracked under:
GitHub Security Advisory: GHSA-9qr9-h5gf-34mp
React Advisory: CVE-2025-55182
Next.js Advisory: CVE-2025-66478
This automated pull request upgrades the affected React and Next.js packages to patched versions that fully remediate the issue.
More Info | [email protected]