Fix React Server Components RCE vulnerability #2
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 - Security Update ### Project Analysis This is a **Next.js** project with a single package.json (not a monorepo). ### Vulnerability Assessment **Affected Package Check:** - ✅ Next.js detected: originally `next@^15.1.3` (VULNERABLE) - ❌ React Flight packages NOT detected: No `react-server-dom-webpack`, `react-server-dom-parcel`, or `react-server-dom-turbopack` dependencies ### Changes Made **Upgraded Next.js to patched version:** - From: `next@^15.1.3` - To: `next@15.5.7` (patched version for 15.5.x) **Reasoning:** The project uses Next.js 15.x, which requires patching. According to the security advisory upgrade rules: - For Next.js 15.5.x → upgrade to `15.5.7` - The project was originally on 15.1.3 and has been upgraded to 15.5.7 - For Next.js projects, React and React-DOM are automatically managed by Next.js, so no manual updates are needed **Files Modified:** - `package.json`: Updated `next` dependency to `15.5.7` (exact version, not caret) - `package-lock.json`: Updated to reflect the new dependency resolution with Next.js 15.5.7 **React Flight packages:** The project does not use React Flight packages (react-server-dom-*), so no additional updates are needed. ### Verification - ✅ Build completed successfully: `npm run build` - No errors - ✅ All dependencies resolved correctly to patched versions - ✅ Lock file properly updated with `next@15.5.7` ### Result The project has been successfully patched and is now protected against the React Flight / Next.js RCE vulnerability (CVE details). Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
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 site. 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