Skip to content

Fix React Server Components RCE vulnerability#4

Draft
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/packages-for-react-flight-rce-0z3r0a
Draft

Fix React Server Components RCE vulnerability#4
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/packages-for-react-flight-rce-0z3r0a

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 aikipedia. 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 Update

### Summary
Updated the aikipedia project to address the React Flight / Next.js RCE advisory (CVE-2025-66478) by upgrading to patched versions of Next.js.

### What Was Done

#### 1. Vulnerability Detection
- **Project Type**: Next.js application
- **Affected Package Found**: `next@16.0.1` was vulnerable
- **Not Affected**: Project does not use React Flight packages (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`)

#### 2. Changes Made

**Modified Files**:
- `package.json` - Updated Next.js versions

**Dependencies Updated**:
- `next`: `16.0.1` → `16.0.7` (patched version for 16.x series)
- `eslint-config-next`: `16.0.1` → `16.0.7` (kept in sync with Next.js)

**React Versions**:
- `react@19.2.0` - Not manually modified (Next.js will supply correct patched version automatically)
- `react-dom@19.2.0` - Not manually modified (Next.js will supply correct patched version automatically)

#### 3. Dependency Installation
- Cleaned and reinstalled all dependencies using npm
- Generated updated `package-lock.json` with patched versions

#### 4. Verification
✅ **Build Successful**: `npm run build` completed without errors
   - Next.js 16.0.7 compiled successfully with Turbopack
   - All pages generated successfully
   - No dependency-related build errors

✅ **Lockfile Verified**: `package-lock.json` confirms:
   - `next@16.0.7` is installed

✅ **Linting**: `npm run lint` executed (pre-existing code quality issues unrelated to dependency update)

✅ **No Tests**: Project does not have test suite configured

### Implementation Notes
- For Next.js projects, React and react-dom are intentionally not manually updated, as Next.js manages these dependencies automatically to ensure compatibility with security patches
- Only the necessary patched versions of Next.js were updated to minimize scope of changes
- The update follows the guidelines for Next.js 16.x: upgrade to 16.0.7 as the patched version
- All changes are backwards compatible; no application code modifications were needed

### Files Changed
- `package.json` (2 dependency version updates)
- `package-lock.json` (generated by npm install)

### Risk Assessment
✅ **Low Risk**: This is a security patch update within the same major/minor version family
✅ **No Breaking Changes**: Version upgrade is to a patch release
✅ **Build Verified**: Production build completes successfully

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)
aikipedia Ready Ready Preview Comment Dec 7, 2025 6:55pm

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Dec 7, 2025

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