Skip to content

Fix React Server Components RCE vulnerability - #1

Draft
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/react-flightnextjs-rce-vulnera-hd5rey
Draft

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

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 open-loveable. 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 Fix

### Summary
Successfully patched the repository to address the React Flight / Next.js RCE advisory (CVE affecting Next.js 15.4.x, 15.3.x, and related versions).

### Vulnerability Assessment
- **Project Type**: Next.js application (v15.4.x)
- **Affected Packages**: Next.js 15.4.3 (vulnerable)
- **React Flight Packages**: None found (project does not use react-server-dom-*)

### Changes Made

#### 1. Updated package.json
- **next**: `15.4.3` → `15.4.8` (patched version for 15.4.x)
- **eslint-config-next**: `15.4.3` → `15.4.8` (matching Next.js version)
- React and react-dom were NOT modified, as Next.js automatically supplies patched versions

#### 2. Updated lockfiles
- **package-lock.json**: Regenerated with `npm install` to resolve all dependencies to patched versions
- **pnpm-lock.yaml**: Verified and already contained correct patched versions
- Confirmed all transitive dependencies resolve correctly

#### 3. Build Verification
- Ran `npm run build` with Next.js 15.4.8
- Build completed successfully with no build errors
- All pre-rendering and API routes compiled correctly

### Technical Details

**Why this fix addresses the vulnerability:**
- The vulnerability (RCE via React Flight/Next.js) was patched in Next.js 15.4.8
- The project was running 15.4.3 (vulnerable) and has been upgraded to 15.4.8
- For Next.js projects, React version management is handled by Next.js itself through peer dependencies
- No manual React version updates were needed for this project

**Files Modified:**
- `package.json` - Updated Next.js dependencies
- `package-lock.json` - Updated lockfile with patched versions
- `pnpm-lock.yaml` - Updated lockfile with patched versions

### Verification
✅ Build completes successfully with Next.js 15.4.8
✅ All dependencies resolve to patched versions in lockfiles
✅ No breaking changes introduced
✅ React and react-dom remain at compatible versions (19.1.0)
✅ No React Flight packages detected (not applicable)

### Notes
- The workspace package at `packages/create-open-lovable/` contains no Next.js or affected packages, so no changes were needed there
- The project uses multiple lockfiles (npm, pnpm, bun) for different environments
- Only npm and pnpm lockfiles were updated (bun CLI not available in environment)
- The pnpm lockfile already had the correct versions from a previous installation

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)
open-loveable Ready Ready Preview Comment Dec 8, 2025 5:56pm

@coderabbitai

coderabbitai Bot commented Dec 8, 2025

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

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