Skip to content

Fix React Server Components RCE vulnerability#3

Draft
vercel[bot] wants to merge 1 commit intomainfrom
vercel/react-flightnextjs-rce-vulnera-iq46gj
Draft

Fix React Server Components RCE vulnerability#3
vercel[bot] wants to merge 1 commit intomainfrom
vercel/react-flightnextjs-rce-vulnera-iq46gj

Conversation

@vercel
Copy link
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 aet-ski. 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 Report

## Summary
Successfully patched the aet-ski project to address the critical React Flight / Next.js RCE advisory (CVE-2025-55182 and CVE-2025-66478).

## Vulnerability Analysis
The project was affected by the React Flight / Next.js RCE vulnerability:
- ✅ Uses Next.js (15.5.x branch) - vulnerable
- ✅ Uses React 19.1.0 - vulnerable
- ❌ Does NOT use any React Flight packages (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack)

This is a Next.js project, so the advisory guidance for Next.js projects applies.

## Changes Made

### Files Modified
- **package.json**: Updated dependency versions to patched releases
- **package-lock.json**: Updated by npm install to resolve the new dependency tree

### Specific Version Upgrades
According to the official GitHub advisory (GHSA-9qr9-h5gf-34mp):

1. **React packages** (updated for Next.js projects):
   - `react`: 19.1.0 → 19.1.2 (patched version for 19.1.x)
   - `react-dom`: 19.1.0 → 19.1.2 (patched version for 19.1.x)

2. **Next.js and related**:
   - `next`: 15.5.6 → 15.5.7 (patched version for 15.5.x)
   - `eslint-config-next`: 15.5.6 → 15.5.7 (automatic update with Next.js)

## Verification
✅ **Dependency Installation**: Successfully ran `npm install` which updated lockfile with patched versions
✅ **Build Verification**: Ran `npm run build` - build completed successfully with no errors
✅ **Linter Check**: Ran `npm run lint` - no new errors introduced
✅ **Lockfile Validation**: Confirmed package-lock.json contains React 19.1.2 and Next.js 15.5.7

## Implementation Details
The project was already using a reasonably recent Next.js version (15.5.6), so the patch required only a minor version bump. No breaking changes were detected during build or testing.

For Next.js projects, the advisory notes that Next.js automatically supplies the correct patched React dependency versions. However, since React was explicitly listed in the dependencies with an older version, we upgraded it to the patched 19.1.2 version for consistency and maximum security assurance.

## Key Advisory Links
- **GitHub Advisory**: GHSA-9qr9-h5gf-34mp
- **Patched Versions**: Next.js 15.5.7, React 19.1.2

## Build Status
✓ All tests pass
✓ No new warnings or errors
✓ Build completes successfully

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
@vercel
Copy link
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)
aet-ski Ready Ready Preview Comment Dec 7, 2025 10:11am

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