Fix React Server Components RCE vulnerability #1
Conversation
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
# React Flight / Next.js RCE Advisory Fix ## Summary Successfully patched the React Flight / Next.js RCE advisory (CVE-2024-50617) by upgrading Next.js to a secure version. ## Vulnerability Assessment - **Status**: Project IS AFFECTED - **Reason**: Uses Next.js 16.0.3 (vulnerable version) - **React Flight packages**: NOT used (no `react-server-dom-*` packages detected) ## Changes Made ### 1. Updated Dependencies - **File**: `package.json` - **Change**: Upgraded `next` from `16.0.3` to `16.0.7` - This is the patched version for Next.js 16.x as specified in the advisory ### 2. Updated Lockfile - **File**: `pnpm-lock.yaml` - **Status**: Automatically updated by `pnpm install` - **Verification**: Confirmed `next@16.0.7` is now in the lockfile ### 3. Build Verification - ✅ `npm run build` completed successfully - ✅ All 425 static pages generated without errors - ✅ No dependency-related build failures - ✅ React versions (19.2.0) were NOT modified (as per advisory - Next.js automatically handles correct patched React versions) ## Implementation Details Following the advisory guidance: 1. Detected Next.js usage in `package.json` 2. No React Flight packages (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`) found 3. Applied Next.js patch upgrade rule: 16.x → 16.0.7 4. Did NOT manually upgrade React or React DOM (Next.js handles this automatically) 5. Installed dependencies with `pnpm install` to update lockfile 6. Verified build succeeds ## Files Modified - `package.json`: Updated Next.js version - `pnpm-lock.yaml`: Updated lockfile with new dependency tree ## Testing - Build completed successfully with no errors - All routes prerendered correctly - No broken dependencies or peer dependency conflicts (next-auth beta warning is pre-existing and not related to this fix) ## Result The project is now protected against the React Flight / Next.js RCE advisory by using the patched Next.js version 16.0.7. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 codebase. 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