Fix React Server Components RCE vulnerability #93
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 Update ### Summary Successfully addressed the React Flight / Next.js RCE advisory by upgrading Next.js to the patched version. ### Analysis The project was affected by the vulnerability: - **Next.js**: Was at vulnerable version `15.5.3`, required upgrade to `15.5.7` - **React Flight packages**: None detected in project (not affected) - **React versions**: `react@19.1.0` and `react-dom@19.1.0` - left unchanged as per Next.js best practices (Next.js handles React versions automatically) ### Changes Made 1. **Updated Next.js from 15.5.3 to 15.5.7** - Modified: `package.json` - Changed `next` dependency from `^15.5.3` to `^15.5.7` - Modified: `pnpm-lock.yaml` - Updated all Next.js-related dependencies to v15.5.7 ### Verification ✅ **Build**: `npm run build` completed successfully with no errors ✅ **Tests**: All 66 tests passed (13 test suites) ✅ **Linting**: `npm run lint:check` passed (7 warnings only, no blocking errors) ✅ **Dependencies**: All dependencies properly resolved in pnpm-lock.yaml ### Files Modified - `package.json` - Next.js version upgrade - `pnpm-lock.yaml` - Lockfile updated with new dependencies ### Notes - This is a Next.js project (not a standalone React Flight app), so React/React-DOM versions were not manually updated - Next.js 15.5.7 (released 2025-12-03) includes the necessary security patches - The project uses `pnpm` for package management - No breaking changes or application logic modifications were required 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 next-auctions. 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