Skip to content

Fix React Server Components RCE vulnerability#37

Draft
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/nextjsreact-flight-rce-vulnera-q2tnrj
Draft

Fix React Server Components RCE vulnerability#37
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/nextjsreact-flight-rce-vulnera-q2tnrj

Conversation

@vercel

@vercel vercel Bot commented Dec 8, 2025

Copy link
Copy Markdown

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 satya-xozl. 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 - Patching Report

## Project Status: AFFECTED - Patched Successfully

### Analysis Summary

This project was assessed for vulnerability to the React Flight / Next.js RCE advisory and found to require patching.

### Vulnerability Detection Results

#### Package Assessment

**Vulnerable packages checked:**
- ✅ `next`: 15.0.3 → **15.0.5** (Vulnerable version detected and upgraded)
- ❌ `react-server-dom-webpack`: Not found
- ❌ `react-server-dom-parcel`: Not found
- ❌ `react-server-dom-turbopack`: Not found

**Other React packages:**
- `react`: ^18.2.0 (Not affected - not a React Flight package)
- `react-dom`: ^18.2.0 (Not affected - not a React Flight package)

### Vulnerability Assessment

The project uses Next.js 15.0.3, which falls within the vulnerable range (Next.js 15.x) specified in the React Flight / Next.js RCE advisory. While the project does not directly use React Flight packages (`react-server-dom-*`), Next.js itself can enable Server Components features that could be affected by this vulnerability.

### Changes Implemented

#### Package Updates

**Updated in `package.json`:**
1. `next`: 15.0.3 → **15.0.5** ✅
2. `eslint-config-next`: 15.0.3 → **15.0.5** ✅

**Lockfile Updates:**
- `package-lock.json`: Updated to resolve the new patched versions
- All transitive dependencies have been updated accordingly

### Patching Strategy Applied

For Next.js 15.0.x projects:
- **Upgrade rule applied**: 15.0.x → `15.0.5` (the patched version)
- **React versions**: Not manually updated as Next.js manages React dependencies

### Verification Status

✅ **Patched version locked in lockfile:**
- The `package-lock.json` has been updated to resolve to the patched Next.js 15.0.5
- All transitive dependencies are consistent with the patched version

### Files Modified

- `package.json`: Updated next and eslint-config-next to 15.0.5
- `package-lock.json`: Updated to reflect new dependency tree

### Build Status

The lockfile updates ensure that the patched versions will be installed. The Next.js configuration remains compatible with all existing application code.

### Security Impact

✅ **Vulnerability addressed**: Next.js has been upgraded to the patched version 15.0.5, which includes fixes for the React Flight / Server Components RCE vulnerability as described in the advisory.

---

*Assessment and patching completed: 2025-12-08*
*Vulnerability: React Flight / Next.js RCE Advisory*
*Patched Version: Next.js 15.0.5*

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
@vercel

vercel Bot commented Dec 8, 2025

Copy link
Copy Markdown
Author

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

Project Deployment Preview Comments Updated (UTC)
satya Ready Ready Preview Comment Dec 8, 2025 4:19pm
satya-371k Ready Ready Preview Comment Dec 8, 2025 4:19pm
satya-protocol Ready Ready Preview Comment Dec 8, 2025 4:19pm
satya-xozl Ready Ready Preview Comment Dec 8, 2025 4:19pm

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