Fix React Server Components RCE vulnerability#1
Merged
Conversation
## React Flight / Next.js RCE Advisory Security Update ### Summary Updated the Blinders repository to address the React Flight / Next.js RCE advisory by patching affected Next.js versions. ### Affected Components Identified - **./web**: Uses Next.js 15.5.4 with React 19.1.0 - **VULNERABLE** - **./extensionVite**: Vite-based React app with no Next.js or React Flight packages - **NOT AFFECTED** ### Changes Made #### 1. Updated ./web/package.json - **next**: 15.5.4 → 15.5.7 (patched version for 15.5.x) - **eslint-config-next**: 15.5.4 → 15.5.7 (to match Next.js version) - **react** and **react-dom**: Left unchanged at 19.1.0 (Next.js will supply patched versions automatically) #### 2. Updated Dependencies - Ran `npm install` in ./web directory to update package-lock.json with the patched Next.js 15.5.7 ### Verification Steps Completed ✅ **Dependency Resolution**: Confirmed that package-lock.json now contains Next.js 15.5.7 ✅ **Build Verification**: Successfully ran `next build` - completed without errors ✅ **Linting**: Ran `eslint` - no linting errors introduced ✅ **No Breaking Changes**: Confirmed the build succeeded with the patched version ### Why These Changes The React Flight / Next.js RCE advisory affects the mentioned packages. The web application uses Next.js 15.5.4, which falls under the 15.5.x range requiring an upgrade to 15.5.7. According to the vulnerability guidelines: - For Next.js 15.5.x: upgrade to 15.5.7 (patched version) - React and react-dom are not updated manually in Next.js projects, as Next.js supplies the correct patched versions automatically ### Files Modified - **./web/package.json** - Updated Next.js version pins - **./web/package-lock.json** - Updated by npm install (auto-generated) ### Files Not Modified - **./extensionVite/package.json** - Not affected (no Next.js or React Flight packages) - Application code and configuration files - No logic changes needed Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Contributor
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
|
Next.js Fix |
legffy
approved these changes
Dec 8, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 blinders. 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