Fix React Server Components RCE vulnerability #1
+7,355
−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 - Patch Applied ### Summary Successfully patched the repository to address the React Flight / Next.js RCE advisory (CVE-2024-xxxxx). ### Vulnerability Assessment **Initial Status**: Project WAS affected - The project used Next.js `16.0.1`, which is vulnerable to the React Flight RCE advisory - No React Flight packages (`react-server-dom-*`) were detected, but Next.js usage made it vulnerable **Vulnerability Details**: - Affected Package: `next@16.0.1` - Required Patch: `next@16.0.7` - Other Packages: No React Flight packages used; `react@19.2.0` and `react-dom@19.2.0` are acceptable ### Changes Made #### Modified Files 1. **package.json** - Updated: `next` from `16.0.1` → `16.0.7` - Reason: Apply patch for Next.js 16.x as per advisory requirements - React versions unchanged (not affected when Next.js is used without React Flight packages) 2. **package-lock.json** - Updated to resolve `next@16.0.7` and all transitive dependencies - Verified lockfile contains the exact patched version #### No Changes Required - ✓ No React Flight packages detected (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`) - ✓ `react` and `react-dom` versions unchanged (Next.js handles React dependency management) - ✓ No other vulnerable packages identified ### Verification **Lockfile Verification**: - `next` resolves to: `16.0.7` ✓ - Integrity hash verified: `sha512-3mBRJyPxT4LOxAJI6IsXeFtKfiJUbjCLgvXO02fV8Wy/lIhPvP94Fe7dGhUgHXcQy4sSuYwQNcOLhIfOm0rL0A==` **Build Status**: - Project uses `npm` as package manager - Lockfile generated and verified - No build errors expected (dependency patch maintains compatibility) ### Implementation Notes 1. The advisory specified that Next.js 16.x should be upgraded to `16.0.7` 2. This is a patch-level upgrade requiring no code changes 3. Next.js automatically manages React dependency resolution, so React versions were not manually adjusted 4. The project had no React Flight packages, eliminating the need for secondary React upgrades 5. All changes are backward compatible - no application logic modifications required ### Files Staged - `.vade-report` - This report - `package.json` - Updated Next.js version - `package-lock.json` - Updated dependency resolution 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 docs. 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