Skip to content

Fix React Server Components RCE vulnerability - #1

Draft
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/nextjs-react-flight-to-patch-r-shmyel
Draft

Fix React Server Components RCE vulnerability#1
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/nextjs-react-flight-to-patch-r-shmyel

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 web-traffic-smm-panel. 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 addressed the React Flight / Next.js RCE advisory by upgrading Next.js to a patched version.

### Vulnerability Detection
- **Next.js Found**: YES - Project uses Next.js
- **Next.js Version**: 15.0.1 → **15.0.5** (patched)
- **React Flight Packages**: None detected
- **Affected by Advisory**: YES (Next.js 15.0.x requires patching)

### Changes Made

#### Modified Files:
1. **package.json**
   - Upgraded `next` from `15.0.1` to `15.0.5`
   - Upgraded `eslint-config-next` from `15.0.1` to `15.0.5` (to match Next.js version)

2. **package-lock.json**
   - Updated lockfile to resolve patched versions
   - Ran `npm install` to regenerate dependency tree

### Rationale for Changes

This project uses Next.js 15.0.1, which is vulnerable to the React Flight RCE advisory. According to the upgrade rules for Next.js 15.0.x, the package needed to be upgraded to 15.0.5.

The project:
- ✅ Uses Next.js (requires patching)
- ❌ Does NOT use React Flight packages (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack)
- ✅ React versions are 18.3.1 (not affected - only React 19.0.0, 19.1.0, 19.1.1, 19.2.0 are vulnerable)
- ✅ No manual React version updates needed (Next.js supplies correct patched React versions automatically)

### Verification

All verification steps completed successfully:

1. **Build Verification**: ✅ `npm run build` completed successfully
   - Next.js 15.0.5 compiled without errors
   - All 6 pages generated successfully
   - Build output shows successful optimization

2. **Linter Verification**: ✅ `npm run lint` passed
   - No new errors introduced
   - Pre-existing warnings remain (unrelated to upgrade)

3. **Lockfile Verification**: ✅ Lockfile correctly resolves patched version
   - `next@15.0.5` present in package-lock.json
   - All dependencies installed successfully

### Implementation Notes

- No application logic changes required
- Patch is purely a version upgrade for security
- Next.js automatically handles React dependency compatibility
- All existing functionality preserved and verified through build/lint

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)
web-traffic-smm-panel Ready Ready Preview Comment Dec 8, 2025 9:16pm

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