Fix React Server Components RCE vulnerability #8
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 - Vulnerability Fix ## Summary Updated the CodeBrainer Next.js project to address the React Flight / Next.js RCE advisory by patching Next.js from a vulnerable version to the patched release. ## Vulnerability Assessment The project was affected by the advisory: - **Next.js 15.5.4** (VULNERABLE) ➜ **15.5.7** (PATCHED) ✅ - **React 19.1.0** (used by Next.js, not directly vulnerable but affected by advisory) - **No React Flight packages** in use (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack not present) ## Changes Made ### Modified Files 1. **package.json** - Upgraded `next` from `15.5.4` to `15.5.7` - Upgraded `eslint-config-next` from `15.5.4` to `15.5.7` (must match Next.js version) 2. **package-lock.json** - Updated lock entries for Next.js 15.5.7 and dependencies - All patched versions now properly resolved ## Implementation Details ### Why These Changes - The vulnerability advisory requires Next.js 15.5.x projects to upgrade to version 15.5.7 - The project was using Next.js 15.5.4, which is vulnerable - No manual React version changes were needed; Next.js 15.5.7 supplies the correct patched React versions automatically - No React Flight packages were present, so only Next.js patching was required ### Testing & Verification ✅ **Build**: `npm run build` completed successfully with all 33 routes properly generated ✅ **Linter**: `npm run lint` runs without any new errors (pre-existing warnings only) ✅ **Dependencies**: `npm install` completed with proper lockfile resolution ✅ **Lockfile**: Verified Next.js 15.5.7 is correctly resolved in package-lock.json ## Notes - The project structure and application logic remain unchanged - Only dependency versions were updated as required by the security advisory - React 19.1.0 and React DOM 19.1.0 were not changed as Next.js 15.5.7 is compatible with these versions and supplies them automatically Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
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 code-brainer. 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]