Fix React Server Components RCE vulnerability#3
Draft
vercel[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
## React Flight / Next.js RCE Advisory - Patching Report ### Vulnerability Detection The project was analyzed for potential vulnerability to the React Flight / Next.js RCE advisory. ### Findings #### Dependencies Checked: 1. **Next.js Status**: ✅ Next.js is used - **VULNERABLE (PATCHED)** - Previous version: `next@15.0.1` (**VULNERABLE**) - Current version: `next@15.0.5` (patched) - Resolved version in lockfile: `15.0.5` - **Status**: PATCHED - Upgraded to the required patched version for Next.js 15.0.x 2. **React Flight Packages**: ❌ None detected - `react-server-dom-webpack`: Not present - `react-server-dom-parcel`: Not present - `react-server-dom-turbopack`: Not present 3. **React Versions**: ✅ Not vulnerable - Current React: `react@18.3.1` - React DOM: `react-dom@18.3.1` - Status: React 18 is not affected by this vulnerability (only React 19.0.0, 19.1.0, 19.1.1, and 19.2.0 are affected) ### Changes Made **Patched Next.js to address React Flight / Next.js RCE Advisory:** Modified files: - `package.json`: Upgraded `next` from `15.0.1` to `15.0.5` - `package.json`: Upgraded `eslint-config-next` from `15.0.1` to `15.0.5` (matching main package version) - `package-lock.json`: Updated to reflect patched dependency versions ### Verification ✅ Project Status: **SECURED** - Next.js upgraded to patched version 15.0.5 (from vulnerable 15.0.1) - Lockfile resolves to patched Next.js version (15.0.5) - No vulnerable React Flight packages in use - React version (18.x) is not affected by the advisory - All dependencies resolved correctly with npm install ### Advisory Compliance This change complies with the React Flight / Next.js RCE advisory: - ✅ Next.js 15.0.x upgraded to patched version 15.0.5 - ✅ React and React DOM versions unchanged (React 18 is not affected) - ✅ No React Flight packages require patching (none in use) ### Files Analyzed and Modified - `./package.json` - Updated Next.js and eslint-config-next versions - `./package-lock.json` - Updated with patched dependency resolutions ### Build Status Dependencies installed successfully with npm. The project is ready for deployment with the security patch applied. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 task-manager. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.
This issue is tracked under:
GitHub Security Advisory: GHSA-9qr9-h5gf-34mp
React Advisory: CVE-2025-55182
Next.js Advisory: CVE-2025-66478
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