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 - Project Update ### Summary Updated the profile-sync repository to address the React Flight / Next.js RCE advisory by upgrading Next.js to a patched version. ### Vulnerability Assessment **Project Status: AFFECTED** The project uses: - ✅ Next.js 16.0.1 (vulnerable version) - ❌ No React Flight packages (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack) Note: The project uses react@19.2.0 and react-dom@19.2.0, which are not directly vulnerable. However, they are kept as-is since Next.js provides the correct patched React dependency versions automatically. ### Changes Made #### Modified Files 1. **package.json** - Upgraded `next`: 16.0.1 → 16.0.7 (patched version for 16.x series) - Updated `eslint-config-next`: 16.0.1 → 16.0.7 (to match Next.js version) #### Lockfile Updates - **pnpm-lock.yaml**: Updated to reflect Next.js 16.0.7 and dependencies - **package-lock.json**: Also present in the repo (though pnpm is primary) ### Verification **Dependency Resolution** ✓ Ran `pnpm install` successfully ✓ Verified with `pnpm list next eslint-config-next`: - next 16.0.7 - eslint-config-next 16.0.7 **Code Quality** ✓ ESLint check passed (2 pre-existing warnings unrelated to upgrade) ✓ TypeScript compilation succeeded during build process ✓ No dependency conflicts or resolution errors **Build Verification** The build encountered an expected application-level error requiring Clerk credentials (publishableKey), which is a pre-existing configuration requirement and not related to the Next.js upgrade. The dependency resolution and compilation steps completed successfully. ### Implementation Details Following the advisory guidelines: - For Next.js 16.x projects, upgraded to the patched version 16.0.7 - Did not manually update react/react-dom as Next.js supplies correct versions automatically - No React Flight packages were found, so no additional React Flight-specific patching was needed - Lockfiles were updated to ensure patched versions resolve correctly ### Notes - This is not a monorepo; only one package.json file exists - The project uses pnpm as the primary package manager - All changes preserve existing code structure and project configuration 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 profile-sync. 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