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 Security Patch Implementation ## Summary Successfully patched the repository to address the React Flight / Next.js RCE advisory (CVE). The project was detected as affected because it depends on Next.js. ## Vulnerability Detection ### Affected Components Found: - ✅ **Next.js**: `next@16.0.6` (VULNERABLE - required patching) - ✅ **ESLint Config Next**: `eslint-config-next@16.0.6` (updated to match) ### Unaffected/Already Safe: - ✅ **React**: `react@19.2.0` (already on patched version - no action needed) - ✅ **React-DOM**: `react-dom@19.2.0` (already on patched version - no action needed) - ❌ **React Flight Packages**: None found (project not using React Flight RSC packages) ## Changes Implemented ### Files Modified: 1. **package.json**: - `next`: `16.0.6` → `16.0.7` (patched version for Next.js 16.x) - `eslint-config-next`: `16.0.6` → `16.0.7` (matching version) 2. **package-lock.json**: - Automatically updated by `npm install` to resolve dependencies with patched versions - Verified that `node_modules/next` resolves to version `16.0.7` ## Verification Results ### Build Status: ✅ PASSED ``` ✓ Compiled successfully in 5.4s ✓ Running TypeScript completed ✓ Generating static pages (7/7) completed ✓ Finalizing page optimization completed ``` The production build completed successfully with Next.js 16.0.7, confirming the patched version works correctly. ### Dependency Resolution: ✅ VERIFIED - npm lockfile correctly resolves to patched version 16.0.7 - All 402 packages audited - Found 0 vulnerabilities ### Linter: ℹ️ Pre-existing issues - 2 errors and 9 warnings (pre-existing, not related to security patches) - No new linting issues introduced by the security update ## Patch Rationale According to the advisory, Next.js 16.x versions require updating to 16.0.7 to address the React Flight RCE vulnerability. The application was using 16.0.6, so it was upgraded to the patched 16.0.7 version per the advisory specifications. The React and React-DOM packages (19.2.0) are already on patched versions and do not require manual updates when using Next.js, as Next.js manages these dependencies automatically. ## Implementation Notes - No React Flight packages (`react-server-dom-*`) are present in the project, so section 3 of the advisory (non-Next React apps) did not apply - React versions were not manually modified, as per the advisory requirement for Next.js projects - The build successfully completes with the patched version, confirming compatibility - All changes follow the project's existing patterns and conventions 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 devkit-hub. 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