Fix React Server Components RCE vulnerability#30
Draft
vercel[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
## React Flight / Next.js RCE Advisory Patch Implementation ### Summary Successfully addressed the React Flight / Next.js RCE advisory (CVE-2025-66478 and CVE-2025-55182) for the fossradar repository. ### Vulnerability Assessment **Status: AFFECTED AND NOW PATCHED** The repository was using Next.js 16.0.4, which falls within the vulnerable 16.x range. The advisory requires all Next.js 16.x versions to be upgraded to 16.0.7. ### Changes Made **Modified Files:** - `package.json` - Updated Next.js and related dependencies to patched versions - `pnpm-lock.yaml` - Updated lockfile to reflect patched versions **Specific Changes:** 1. Updated `next` from `^16.0.4` to `^16.0.7` (patched version for 16.x) 2. Updated `eslint-config-next` from `^16.0.4` to `^16.0.7` (to match Next.js version) ### Vulnerability Details - **CVE-2025-66478**: Next.js Server Functions deserialization RCE - **CVE-2025-55182**: React Server Components deserialization RCE - **Affected Packages**: Next.js 16.0.0 through 16.0.6 - **Fixed in**: Next.js 16.0.7 ### Non-Affected Components - The repository does not use any React Flight / React Server Components packages: - `react-server-dom-webpack` ✗ - `react-server-dom-parcel` ✗ - `react-server-dom-turbopack` ✗ - React and React-DOM are not directly vulnerable; they were only updated automatically by Next.js to 19.2.0 - No React Flight packages require special handling ### Verification ✅ **Build Status**: Production build completes successfully ✅ **Dependency Resolution**: All dependencies resolve correctly to patched versions ✅ **Next.js Version**: Confirmed at 16.0.7 in node_modules and lockfile ✅ **React Versions**: Correctly at 19.2.0 (no manual intervention needed) Build output confirms: - Next.js 16.0.7 with Turbopack enabled - 83 static pages generated successfully - TypeScript validation passed - All API routes and dynamic routes functioning correctly ### Implementation Notes 1. The fix was applied by updating package.json to the patched version specification 2. Running the build process automatically installed the correct versions via pnpm 3. The lockfile (pnpm-lock.yaml) was automatically updated with the patched versions 4. React and React-DOM versions were automatically managed by Next.js and did not require manual updates 5. No application logic changes were necessary ### Conclusion The repository is now protected against the React Flight / Next.js RCE vulnerability. All affected dependencies have been upgraded to patched versions, and the build system confirms successful resolution of all dependencies. 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 radar. 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