Skip to content

Fix React Server Components RCE vulnerability#1

Merged
TechBeme merged 1 commit intomainfrom
vercel/react-flight-rce-vulnerability-cerwvd
Feb 2, 2026
Merged

Fix React Server Components RCE vulnerability#1
TechBeme merged 1 commit intomainfrom
vercel/react-flight-rce-vulnerability-cerwvd

Conversation

@vercel
Copy link
Copy Markdown

@vercel vercel Bot commented Dec 8, 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 kickstarter. 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 - Security Patch Applied

### Summary
The project has been successfully patched to address the React Flight / Next.js RCE advisory. Next.js was updated from vulnerable version 16.0.1 to patched version 16.0.7.

### Vulnerability Assessment

**Affected Packages Detection:**
✓ Next.js: DETECTED - updated from `next@16.0.1` to `next@16.0.7`
✗ React Flight packages: NOT DETECTED
  - `react-server-dom-webpack`: Not present
  - `react-server-dom-parcel`: Not present
  - `react-server-dom-turbopack`: Not present

### Applied Changes

**Files Modified:**
1. `website/package.json` - Updated Next.js and ESLint config versions
2. `website/package-lock.json` - Updated by npm to reflect patched versions

**Version Updates:**
- `next`: `16.0.1` → `16.0.7` (patched)
- `eslint-config-next`: `16.0.1` → `16.0.7` (aligned with next version)
- `react`: `19.2.0` (no change required - not vulnerable)
- `react-dom`: `19.2.0` (no change required - not vulnerable)

### Upgrade Rationale

According to the React Flight / Next.js RCE advisory:
- Next.js 16.x requires upgrade to `16.0.7` ✅ Applied
- No vulnerable React Flight packages in use, so no additional patches needed
- React and react-dom versions are appropriate and not vulnerable

### Verification

**Project Status:**
- Next.js: ✅ PATCHED (16.0.7)
- React Flight usage: ✅ NOT AFFECTED
- Build compatibility: ✅ Ready

### Files Analyzed and Modified
- `./website/package.json` - Updated Next.js and ESLint config to patched versions
- `./website/package-lock.json` - Updated by dependency manager

### Conclusion

The repository is now compliant with the React Flight / Next.js RCE security advisory. The project was using a vulnerable version of Next.js (16.0.1) and has been successfully upgraded to the patched version (16.0.7). No further action is required.

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

vercel Bot commented Dec 8, 2025

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

Project Deployment Preview Comments Updated (UTC)
kickstarter Ready Ready Preview Comment Dec 8, 2025 7:02pm

@TechBeme TechBeme marked this pull request as ready for review February 2, 2026 21:12
@TechBeme TechBeme merged commit e88dcda into main Feb 2, 2026
2 checks passed
TechBeme added a commit that referenced this pull request Apr 28, 2026
…lity-cerwvd

Fix React Server Components RCE vulnerability
TechBeme added a commit that referenced this pull request Apr 28, 2026
…lity-cerwvd

Fix React Server Components RCE vulnerability
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.

1 participant