Fix React Server Components RCE vulnerability#16
Merged
Conversation
## React Flight / Next.js RCE Advisory Assessment ### Project Status: NOT VULNERABLE **Summary**: After analyzing the project dependencies, no changes were required because the project is already protected against the React Flight / Next.js RCE advisory. ### Vulnerability Detection Results #### 1. Next.js Check - **Status**: ✅ PROTECTED - **Current Version**: `next@16.0.7` - **Required Version**: `16.0.7` (for Next.js 16.x) - **Assessment**: Already at the patched version. No upgrade needed. #### 2. React Flight Packages Check - **Status**: ✅ NOT AFFECTED - **Packages Checked**: - `react-server-dom-webpack`: Not found - `react-server-dom-parcel`: Not found - `react-server-dom-turbopack`: Not found - **Assessment**: Project does not use any vulnerable React Flight packages. #### 3. React Version Check - **Status**: ✅ SAFE - **Current Versions**: - `react@19.2.0` (safe version) - `react-dom@19.2.0` (safe version) - **Assessment**: All React versions are outside the vulnerable ranges (19.0.0, 19.1.0, 19.1.1, 19.2.0 vulnerable versions are not used). ### Conclusion The project `minotor.dev` is **already protected** against the React Flight / Next.js RCE advisory. The Next.js version is already at the patched `16.0.7`, and there are no vulnerable React Flight packages in the dependency tree. No code changes, dependency updates, or build verifications were necessary. ### Files Modified None - no changes required. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Contributor
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
aubryio
marked this pull request as ready for review
December 8, 2025 20:48
aubryio
self-requested a review
December 8, 2025 20:48
aubryio
approved these changes
Dec 8, 2025
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
1 participant
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 minotor.dev. 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