Fix React Server Components RCE vulnerability #10
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 Security Update ### Summary Updated the aiex repository to address the React Flight / Next.js RCE advisory by upgrading Next.js to a patched version. ### Vulnerability Assessment - **Project Type**: Next.js application (single package.json) - **Affected**: ✓ Yes - Uses Next.js 15.5.6 - **React Flight Packages**: ✗ No - Not using react-server-dom-webpack, react-server-dom-parcel, or react-server-dom-turbopack - **Action Taken**: Upgraded Next.js only (React/React-DOM not modified per Next.js update guidelines) ### Changes Made #### Modified Files 1. **package.json** - Upgraded `next` from `15.5.6` to `15.5.7` (patched version) - No changes to `react` or `react-dom` - Next.js handles React dependency versioning 2. **package-lock.json** - Automatically updated to reflect Next.js 15.5.7 installation - All @next/* dependencies updated to matching 15.5.7 versions - Lockfile resolves correctly to patched Next.js version ### Verification ✓ Dependencies installed successfully using `npm install` ✓ Build completed successfully with `npm run build` ✓ All 91 static pages generated without errors ✓ Lockfile contains correct patched versions: - `"next": "15.5.7"` in package-lock.json - All @next/* packages at version 15.5.7 ### Implementation Details - Applied the specific patched version rule: next 15.5.x → 15.5.7 - Did NOT modify react or react-dom versions per Next.js recommendations - Project is not a monorepo, single package.json handled - No vulnerable React Flight packages detected, only Next.js update needed ### Files Modified - `package.json` - Updated Next.js version - `package-lock.json` - Updated by npm during install ### Build Status ✓ Compilation successful in 25.6s ✓ 91 static pages generated ✓ No errors or breaking changes ✓ Application ready for deployment 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 aiex. 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