Fix React Server Components RCE vulnerability#1
Draft
vercel[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
React Flight / Next.js RCE Advisory Mitigation VULNERABILITY DETECTION RESULTS: This repository IS affected by the React Flight / Next.js RCE advisory. Project uses: - ✅ Next.js (version 15.3.x) - AFFECTED - ✅ React (version 18.3.1) - Not vulnerable but required by Next.js - ✅ React-DOM (version 18.3.1) - Not vulnerable but required by Next.js - ❌ React Flight packages (react-server-dom-*) - NOT USED CHANGES APPLIED: Modified Files: 1. package.json - Updated Next.js from "^15.3.3" to "15.3.6" (pinned to patched version) - This ensures the project uses the patched version for the 15.3.x minor 2. package-lock.json - Updated to reflect the Next.js 15.3.6 resolution - Additional dependency updates for Next.js 15.3.6 compatibility RATIONALE: Since this is a Next.js 15.3.x project, the upgrade path requires: - Next.js 15.3.x → 15.3.6 (patched version) According to the advisory, Next.js handles React and React-DOM versions automatically, so they were left as-is. The React Flight packages are not used in this project, so no additional changes were needed for those. VERIFICATION: ✅ Build completed successfully with `npm run build` ✅ All dependencies resolved correctly ✅ No build errors or warnings related to vulnerability ✅ Package-lock.json updated to pinned patched version The project is now protected against the React Flight / Next.js RCE vulnerability. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket 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 docs. 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