Skip to content

Fix React Server Components RCE vulnerability#1

Draft
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/react-flight-rce-vulnerability-ne9r7q
Draft

Fix React Server Components RCE vulnerability#1
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/react-flight-rce-vulnerability-ne9r7q

Conversation

@vercel
Copy link
Copy Markdown
Contributor

@vercel vercel Bot commented Dec 7, 2025

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 portfolio. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.

This issue is tracked under:

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

React Flight / Next.js RCE Advisory - Remediation Report

VULNERABILITY STATUS: ✅ FIXED

SUMMARY:
This project was affected by the React Flight / Next.js RCE advisory due to using Next.js 15.3.1.
The vulnerability has been remediated by upgrading Next.js to the patched version.

PROJECT ANALYSIS:

1. Project Type: Next.js Application (Single-package, not a monorepo)

2. Affected Packages Detected:
   ✅ Next.js: next@^15.3.1 (VULNERABLE)
   ❌ React Flight packages: None present
      - No react-server-dom-webpack
      - No react-server-dom-parcel
      - No react-server-dom-turbopack

3. Vulnerability Assessment Details:

   a) Next.js Version Status:
      BEFORE: next@^15.3.1 (VULNERABLE - 15.3.x vulnerable versions)
      AFTER:  next@15.3.6  (PATCHED)
      
      According to the advisory, Next.js 15.3.x versions required patching:
      - 15.3.x → 15.3.6 ✅ Applied
      
   b) React Flight Packages:
      - Status: NOT USED
      - No react-server-dom-* packages detected
      - No patching required for this category

4. Changes Made:

   Modified Files:
   - package.json:
     * next: ^15.3.1 → 15.3.6
     
   - package-lock.json:
     * Updated to reflect patched dependency versions
     * Verified next@15.3.6 is correctly resolved

5. Dependency Resolution:
   
   Final resolved versions:
   - next@15.3.6 ✅ (patched version)
   - react@19.0.0 (managed by Next.js)
   - react-dom@19.0.0 (managed by Next.js)
   
   npm list next output confirms:
   ```
   @once-ui-system/magic-portfolio@2.2.0
   +-- @once-ui-system/core@1.3.15
   | `-- next@15.3.6 deduped
   `-- next@15.3.6
   ```

6. Build Verification:
   ✅ Build completed successfully with Next.js 15.3.6
   ✅ Static pages generated (17 pages)
   ✅ Production build finalized without dependency errors
   
   Note: Pre-existing ESLint configuration warning (unrelated to RCE advisory)
   has no impact on the security fix.

CONCLUSION:
The @once-ui-system/magic-portfolio project has been successfully patched against the 
React Flight / Next.js RCE advisory. The vulnerable Next.js 15.3.1 dependency has been 
upgraded to the patched version 15.3.6. The build completes successfully, confirming 
the patch resolves correctly and does not introduce compatibility issues.

The project is now protected from the React Flight / Next.js RCE vulnerability.

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
@vercel
Copy link
Copy Markdown
Contributor Author

vercel Bot commented Dec 7, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
portfolio Ready Ready Preview Comment Dec 7, 2025 10:44am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants