Fix React Server Components RCE vulnerability - #5
Draft
vercel[bot] wants to merge 1 commit into
Draft
Conversation
# React Flight / Next.js RCE Advisory Fix Report ## Project Analysis ### Vulnerability Status: ✅ FIXED This Next.js project was vulnerable to the React Flight / Next.js RCE advisory and has been patched. ## Detailed Findings ### Original Vulnerable Versions - **Next.js:** 15.5.4 → **15.5.7** (patched) - **React:** 19.1.0 → **19.1.2** (patched) - **React DOM:** 19.1.0 → **19.1.2** (patched) - **eslint-config-next:** 15.5.4 → **15.5.7** (patched) ### Changes Applied According to the React Flight RCE advisory, Next.js 15.5.x versions up to 15.5.6 are vulnerable. The fix required upgrading to **15.5.7**, which is the patched version for the 15.5.x minor version. #### Files Modified: 1. **package.json** - Updated `next` from 15.5.4 to 15.5.7 - Updated `react` from 19.1.0 to 19.1.2 - Updated `react-dom` from 19.1.0 to 19.1.2 - Updated `eslint-config-next` from 15.5.4 to 15.5.7 2. **package-lock.json** - Updated all dependency lockfile entries to resolve the patched versions - Verified that Next.js 15.5.7 and React 19.1.2 are correctly locked ### Why These Changes According to the advisory requirements: - Next.js 15.5.x versions are vulnerable and must be upgraded to 15.5.7 - For Next.js projects, React versions are automatically managed by Next.js, but React 19.1.0 contained RCE vulnerabilities that required patching to 19.1.2 - The project did not use React Flight packages directly (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`), so only Next.js-managed versions needed updating ### Verification - Build system initiated successfully with patched versions - Dependencies resolve correctly in lockfile - No additional configuration changes required - Project follows Next.js patterns correctly ## Summary The project was vulnerable to the React Flight / Next.js RCE advisory with: - Next.js 15.5.4 (vulnerable) - React/React DOM 19.1.0 (vulnerable) Applied the recommended patches: - Upgraded to Next.js 15.5.7 - Upgraded to React 19.1.2 and React DOM 19.1.2 - Updated lockfile to reflect patched versions The project is now **fully compliant** with the advisory and protected against the 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.
|
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 common-lobbyist. 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