Fix React Server Components RCE vulnerability - #1
Draft
vercel[bot] wants to merge 1 commit into
Draft
Conversation
## React Flight / Next.js RCE Advisory - Vulnerability Patch Applied ### Vulnerability Status: PATCHED ✅ This project required a security update to address the React Flight / Next.js RCE advisory. ### Changes Applied **Package Updates:** - ✅ Upgraded `next` from `15.5.0` → `15.5.7` (patched version for 15.5.x minor) - ✅ React/React-DOM remain at 19.1.0 (no changes needed, handled by Next.js) - ✅ No React Flight packages (`react-server-dom-*`) in use ### Analysis Details **Vulnerability Detection:** - Project uses Next.js (version was 15.5.0 - vulnerable, now patched to 15.5.7) - Project does NOT use any `react-server-dom-webpack`, `react-server-dom-parcel`, or `react-server-dom-turbopack` packages - No monorepo structure detected **Upgrade Rules Applied:** For Next.js 15.5.x releases, the patched version is `15.5.7`. The project was on `15.5.0` and has been upgraded to the patched version. **Files Modified:** 1. `package.json` - Updated Next.js version from `15.5.0` to `15.5.7` 2. `package-lock.json` - Updated lock entries for Next.js and related packages ### Verification ✅ Package versions updated correctly in package.json ✅ Lock file regenerated with patched Next.js version (15.5.7) ✅ Build verification: Build completes successfully (warnings about missing env variables are pre-existing, unrelated to this patch) ✅ Package tree verification: All dependencies resolve correctly ### Implementation Notes - This is a Next.js patch update within the same minor version (15.5.x) - React versions (19.1.0) were not modified as Next.js provides compatible patched versions - The update addresses the RCE vulnerability without requiring major version upgrades - No application code changes were necessary ### Summary Successfully patched the React Flight / Next.js RCE vulnerability by upgrading Next.js to version 15.5.7, the patched version for the 15.5.x minor release. 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 geoart. 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