Fix React Server Components RCE vulnerability #1111
Merged
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 - Analysis and Resolution ### Project Analysis This project (hiro-systems-docs) has been analyzed for vulnerability to the React Flight / Next.js RCE advisory. ### Findings **Affected Status: NOT VULNERABLE - Already Patched** The project is a Next.js application with the following relevant dependencies: - **next**: 15.3.6 (patched version) - **react**: 19.0.0 (no manual update needed for Next.js) - **react-dom**: 19.0.0 (no manual update needed for Next.js) - **React Flight packages**: None detected (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack not in use) ### Resolution **No changes were required.** The project is already running the patched version of Next.js for the 15.3.x minor series: - Next.js 15.3.x: ✅ Already at 15.3.6 (patched version) - No React Flight packages in use - React and React DOM dependencies are managed by Next.js and are at compatible versions ### Verification Confirmed the following: 1. Next.js is at version 15.3.6 (the patched version for 15.3.x releases) 2. No vulnerable React Flight packages (react-server-dom-*) are present in dependencies 3. React 19.0.0 is compatible with Next.js 15.3.6 4. No manual React updates needed (Next.js manages React versions automatically) ### Conclusion This project requires no modifications to address the React Flight / Next.js RCE advisory. It is already running patched software versions. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Contributor
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
rafaelcr
approved these changes
Dec 8, 2025
ryanwaits
approved these changes
Dec 8, 2025
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 hiro-systems-docs. 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