-
Notifications
You must be signed in to change notification settings - Fork 0
Fix React Server Components CVE vulnerabilities #8
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
base: main
Are you sure you want to change the base?
Conversation
Updated dependencies to fix Next.js and React CVE vulnerabilities. The fix-react2shell-next tool automatically updated the following packages to their secure versions: - next - react-server-dom-webpack - react-server-dom-parcel - react-server-dom-turbopack All package.json files have been scanned and vulnerable versions have been patched to the correct fixed versions based on the official React advisory. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR addresses critical security vulnerabilities in React Server Components (CVE-2025-55182 and CVE-2025-66478) by upgrading Next.js to patched versions across the monorepo. The automated security patch updates Next.js dependencies to versions that remediate a remote code execution (RCE) vulnerability affecting the React Flight protocol.
Key Changes:
- Upgraded Next.js from 14.2.32 to 14.2.35 for projects using Next.js 14.x
- Upgraded Next.js from 15.3.5 to 15.3.8 for the pay-test-exchange app
- Upgraded Next.js from 15.6.0-canary.29 to 15.6.0-canary.60 for the laboratory app
Reviewed changes
Copilot reviewed 11 out of 12 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| pnpm-lock.yaml | Updated lock file with new Next.js versions and resolved dependencies including @next/swc binaries, @next/env, and @next/third-parties references |
| apps/demo/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
| apps/laboratory/package.json | Updated Next.js version from 15.6.0-canary.29 to 15.6.0-canary.60 |
| apps/pay-test-exchange/package.json | Updated Next.js version from 15.3.5 to 15.3.8 |
| examples/next-wagmi-solana-bitcoin-app-router/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
| examples/next-wagmi-app-router/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
| examples/next-ethers-app-router/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
| examples/next-ep-app-router/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
| examples/next-bitcoin-app-router/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
| examples/next-ak-basic-up-app-router/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
| examples/next-ak-basic-sign-client-app-router/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
| examples/next-ak-basic-app-router/package.json | Updated Next.js version from 14.2.32 to 14.2.35 |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
joe10832
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 appkit-demo. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.
This issue is tracked under:
This automated pull request upgrades the affected React and Next.js packages to patched versions that fully remediate the issue.
More Info | [email protected]