Fix React Server Components RCE vulnerability#1
Draft
vercel[bot] wants to merge 1 commit intomasterfrom
Draft
Conversation
# React Flight / Next.js RCE Advisory Patch Report ## Summary Successfully patched the project to address the React Flight / Next.js RCE advisory. ## Vulnerability Detection Results ### Affected Components Found: - ✅ **Next.js 15.2.3** - AFFECTED and PATCHED - ❌ React Flight packages (react-server-dom-*) - Not used in this project - ✅ React versions (18.3.1) - Not vulnerable (only React 19.0.0-19.2.0 are affected) ### Project Structure: - Single package.json (not a monorepo) - Project type: Next.js application - Build system: Next.js with Turbopack - Package manager: npm (uses package-lock.json) ## Changes Made ### Modified Files: 1. **package.json** - Updated `next` from `15.2.3` to `15.2.6` - This is the patched version for Next.js 15.2.x series as specified in the advisory 2. **package-lock.json** - Updated lockfile to resolve the new Next.js version - Dependencies properly resolved with patched version ### Why These Changes: - The project uses Next.js 15.2.3, which is vulnerable to the RCE advisory - According to the patch rules, Next.js 15.2.x should be upgraded to 15.2.6 - React and react-dom were not modified because: - They are React 18 (not vulnerable - only 19.0.0-19.2.0 are affected) - Next.js automatically supplies the correct React versions - Project does not use React Flight packages ## Verification ### Build Verification: ✅ Successfully ran `npm run build` - Build completed successfully with Next.js 15.2.6 - No build errors or warnings related to the upgrade - All pages pre-rendered correctly (11/11 static pages generated) ### Lockfile Verification: ✅ Verified package-lock.json contains the patched version - Confirmed Next.js 15.2.6 is the resolved version in lockfile - All dependencies properly installed and resolved ### No Breaking Changes: - Only version bump to a patch release - No API changes or compatibility issues - Existing code structure preserved - No application logic modifications needed ## Next Steps for PR The changes are ready to merge: 1. Stage: `git add package.json package-lock.json .vade-report` 2. Create PR with these changes to address the vulnerability 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 v0-miguel-angel-murillo-x4f9rhhsv1c. 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