Skip to content

Fix React Server Components RCE vulnerability#1

Draft
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/dependencies-for-react-flight-jrxxo2
Draft

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

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 boolog. 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 Patch

### Summary
Successfully updated the repository to address the React Flight / Next.js RCE advisory (CVE-2025-66478).

### Vulnerabilities Detected
- **Next.js 15.3.3** - Project was using affected version of Next.js
- **React 19.0.0** - Vulnerable React version that was used

### Changes Made

#### 1. Package Dependency Updates
Modified `package.json` to patch the vulnerable Next.js version:
- Updated `next` from `^15.3.3` to `^15.3.6` (dependencies)
- Updated `eslint-config-next` from `15.3.3` to `15.3.6` (devDependencies)

#### 2. Lockfile Updates
Ran `npm install` to resolve dependencies:
- The caret constraint (^15.3.6) allowed npm to install `next@15.5.7`, which is a patched version that includes the security fix
- React and react-dom were automatically updated by Next.js to `19.1.0` (patched versions)
- No React Flight/RSC packages (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`) were found in the project

#### 3. Verification Steps Completed

**Build Verification:**
- ✅ `npm run build` completed successfully
- ✅ All 12 static pages generated without errors
- ✅ No build-time dependency resolution errors

**Linting:**
- ✅ `npm run lint` passed
- ✅ Only pre-existing warnings about image optimization (unrelated to security patch)

**Final Resolved Versions:**
- `next@15.5.7` (patched, resolves ^15.3.6 constraint)
- `react@19.1.0` (patched, not vulnerable)
- `react-dom@19.1.0` (patched, not vulnerable)

### Implementation Details

The project was identified as affected because:
1. It depends on Next.js (found `next` in dependencies)
2. It does NOT use React Flight packages (no `react-server-dom-*` packages found)

Per the advisory instructions:
- For Next.js projects, manual React version updates are NOT performed since Next.js provides patched versions automatically
- The Next.js version was upgraded from 15.3.3 to 15.3.6 as per the upgrade rules for 15.3.x
- The caret constraint allows resolution to 15.5.7, which contains the security fix

### Files Modified
- `package.json` - Updated `next` and `eslint-config-next` versions
- `package-lock.json` - Updated with resolved patched versions (auto-generated by npm install)

### No Changes Required
- No React version manual updates (handled by Next.js)
- No React Flight packages present
- No application code changes needed

### Security Impact
The repository is now protected against the React Flight / Next.js RCE vulnerability (CVE-2025-66478). The patched Next.js version resolves the security issue without requiring major version upgrades.

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)
boolog Ready Ready Preview Comment Dec 8, 2025 3:24pm

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