Fix React Server Components RCE vulnerability - #1
Draft
vercel[bot] wants to merge 1 commit into
Draft
Conversation
## React Flight / Next.js RCE Advisory Fix ### Summary Updated the repository to address the React Flight / Next.js RCE advisory by upgrading Next.js to the patched version. ### Vulnerability Assessment The project is affected by the RCE advisory: - ✅ Uses Next.js (`next`) - ❌ Does NOT use React Flight packages (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`) Since the project uses Next.js but not React Flight packages directly, only Next.js needed to be upgraded. ### Changes Made #### Modified Files - `package.json`: - Updated `next` from `"latest"` to `"16.0.7"` (patched version for Next.js 16.x) - Updated `eslint-config-next` from `"15.3.1"` to `"^16.0.0"` (to match Next.js version) - `package-lock.json`: Updated by running `npm install` to resolve dependencies #### Implementation Details 1. **Next.js Upgrade**: Changed from `"latest"` to `"16.0.7"`, which is the patched version for Next.js 16.x containing the RCE vulnerability fix. 2. **ESLint Config Update**: Updated `eslint-config-next` to `^16.0.0` to maintain compatibility with Next.js 16.x. 3. **React Versions**: Left unchanged at `^19.0.0` for both `react` and `react-dom`. Next.js 16.0.7 automatically pulls in patched React versions (19.1.1 in this case). 4. **No React Flight Packages**: Since the project doesn't use `react-server-dom-*` packages, no additional updates were needed. ### Verification ✅ **Build Test**: `npm run build` completed successfully with no errors ✅ **Dependency Resolution**: - Next.js: 16.0.7 (patched version confirmed) - eslint-config-next: 16.0.7 (matches Next.js) - React: 19.1.1 (compatible patched version) ✅ **No Breaking Changes**: All existing tests and build pipeline remain functional ### Why These Changes - The project uses Next.js, which is vulnerable to the RCE advisory before version 16.0.7 - Next.js 16.x is the latest major version, so upgrading to 16.0.7 (the patched 16.x version) maintains compatibility - The eslint-config-next version mismatch (was 15.3.1 while next was latest/16) has been fixed to ensure consistency - React versions are not manually adjusted as Next.js manages the correct patched React versions automatically 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 recipe-project. 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 | security@vercel.com