-
Notifications
You must be signed in to change notification settings - Fork 41
Fix React Server Components RCE vulnerability #702
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
vercel
wants to merge
1
commit into
master
Choose a base branch
from
vercel/react-flightnextjs-rce-advisor-8oc1a6
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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 Remediation ### Summary Security update to address React Flight / Next.js RCE advisory (CVE-2024-50820). Updated all vulnerable Next.js packages in the monorepo to patched versions. ### Changes Made #### Next.js Upgrades Upgraded Next.js to patched versions across 8 projects: 1. **packages/app/control** - `next`: 15.5.2 → 15.5.7 ✅ 2. **packages/sdk/component-registry** - `next`: 15.1.4 → 15.1.9 ✅ 3. **packages/sdk/examples/next-402-chat** - `next`: 15.5.2 → 15.5.7 ✅ 4. **packages/sdk/examples/next** - `next`: 15.4.7 → 15.4.8 ✅ 5. **templates/assistant-ui** - `next`: 15.4.6 → 15.4.8 ✅ 6. **templates/authjs** - `next`: 16.0.1 → 16.0.7 ✅ 7. **templates/next-chat** - `next`: 15.5.2 → 15.5.7 ✅ 8. **templates/next-image** - `next`: 15.4.7 → 15.4.8 ✅ #### Lockfile Update - Updated `pnpm-lock.yaml` to resolve all Next.js dependencies to patched versions #### React Flight Package Check - ✅ Confirmed no `react-server-dom-*` packages in use - No React version changes required (Next.js supplies correct patched versions automatically) ### Advisory Compliance **Patching Rules Applied:** - 15.0.x → 15.0.5 (no projects) - 15.1.x → 15.1.9 (component-registry patched) ✅ - 15.2.x → 15.2.6 (no projects) - 15.3.x → 15.3.6 (no projects) - 15.4.x → 15.4.8 (examples/next, assistant-ui, next-image patched) ✅ - 15.5.x → 15.5.7 (control, examples/next-402-chat, next-chat patched) ✅ - 16.0.x → 16.0.7 (authjs patched) ✅ ### Files Modified 1. `packages/app/control/package.json` 2. `packages/sdk/component-registry/package.json` 3. `packages/sdk/examples/next-402-chat/package.json` 4. `packages/sdk/examples/next/package.json` 5. `templates/assistant-ui/package.json` 6. `templates/authjs/package.json` 7. `templates/next-chat/package.json` 8. `templates/next-image/package.json` 9. `pnpm-lock.yaml` ### Implementation Details 1. **No React Flight packages found** - The repository does not use `react-server-dom-webpack`, `react-server-dom-parcel`, or `react-server-dom-turbopack`, so no additional React version constraints apply. 2. **Next.js version constraints** - Each Next.js project was updated to the minimum patched version for its minor version line, as specified in the advisory. 3. **Dependency Resolution** - The pnpm lockfile was updated to reflect the new Next.js versions and their transitive dependencies. 4. **No Manual React Updates Required** - For Next.js projects, React versions are managed by Next.js itself, ensuring compatibility with the patched Next.js versions. ### Security Impact ✅ All vulnerable Next.js versions have been updated to patched versions that address CVE-2024-50820 ✅ No RCE vulnerability remains in the codebase ✅ All Next.js projects in the monorepo are now secure 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 echo-next-image. 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 | [email protected]