Fix React Server Components RCE vulnerability#26
Open
vercel[bot] wants to merge 1 commit intomainfrom
Open
Conversation
React Flight / Next.js RCE Advisory Fix VULNERABILITY ASSESSMENT: This project was assessed for vulnerability to the React Flight / Next.js RCE advisory (https://github.com/vercel/next.js/security/advisories). FINDINGS: The project contains Next.js and was affected by the advisory, requiring an upgrade. AFFECTED PACKAGES DETECTED: - next: 15.5.4 (vulnerable range) NOT AFFECTED: - React Flight packages: None detected (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack) - React/React-DOM: Not affected - these are only patched when React Flight packages require updates CHANGES IMPLEMENTED: 1. Updated package.json - next: 15.5.4 → 15.5.7 (patched version for 15.5.x) - eslint-config-next: 15.5.4 → 15.5.7 (matching Next.js version) 2. Updated package-lock.json - Ran `npm install` to generate updated lockfile with patched versions - Verified Next.js 15.5.7 is resolved in dependencies 3. Build Verification - Ran `npm run build` with Turbopack - Build completed successfully with no errors - All static pages generated correctly TECHNICAL DETAILS: - The project is a Next.js 15.5 application - No React Flight packages are used, so React/React-DOM were not manually upgraded - Next.js 15.5.7 resolves React dependencies correctly for this codebase - React 19.1.0 is acceptable in this context since React Flight packages are not used CONCLUSION: The project has been patched against the React Flight RCE advisory. Next.js has been upgraded from 15.5.4 to 15.5.7, and the build completes successfully with all dependencies properly resolved. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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 dashboard. 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