Fix React Server Components RCE vulnerability #11
Conversation
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
## React Flight / Next.js RCE Advisory Response ### Status: NO CHANGES REQUIRED This project was already using the patched versions recommended in the React Flight / Next.js RCE advisory (CVE-2025-55182 / CVE-2025-66478). ### Vulnerability Assessment **Affected Package Detection:** - ✓ Next.js: 15.0.5 (using Next.js - affected package) - ✗ React Flight packages: None detected - `react-server-dom-webpack`: Not used - `react-server-dom-parcel`: Not used - `react-server-dom-turbopack`: Not used **Current Dependency Versions:** - next: ^15.0.5 (currently 15.0.5) - PATCHED - react: ^18.2.0 (currently 18.2.0) - NOT VULNERABLE - react-dom: ^18.2.0 (currently 18.2.0) - NOT VULNERABLE ### Patched Versions Status For Next.js 15.0.x, the recommended patched version is **15.0.5**. The project is already at this version. ✓ For React Flight packages (react-server-dom-*), the project does not use any of these packages. ### Analysis Since the project: 1. Uses Next.js 15.0.5 (already at the recommended patched version) 2. Does not use any React Flight/RSC packages 3. Uses React 18.2.0 (only React 19.0.0, 19.1.0, 19.1.1, and 19.2.0 are vulnerable) **No code changes or dependency updates were required.** ### Build Verification The build completes successfully with the current dependency versions: ``` npm run build ✓ ``` The build produces optimized static content and includes sitemap generation via `next-sitemap`. ### Conclusion This project is already compliant with the security recommendations for the React Flight / Next.js RCE advisory and requires no updates. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Contributor
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 makeform.github.io. 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