Fix React Server Components RCE vulnerability#1
Draft
vercel[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
# React Flight / Next.js RCE Advisory - Impact Assessment ## Project Status: NOT AFFECTED After a comprehensive analysis of the headkit-storefront repository, this project **does not require any changes** in response to the React Flight / Next.js RCE advisory. ## Vulnerability Assessment ### Packages Checked: 1. **Next.js**: Version 16.0.7 ✅ - The project uses `next@16.0.7`, which is the patched version for the 16.x release - No action needed 2. **React Flight / React Server Components**: - `react-server-dom-webpack`: NOT present - `react-server-dom-parcel`: NOT present - `react-server-dom-turbopack`: NOT present - No action needed 3. **React and React DOM**: Versions 19.2.0 ✅ - While the project uses React 19.2.0 and React DOM 19.2.0, these versions are NOT vulnerable themselves - The vulnerability only affects React Flight packages (react-server-dom-*), which are not used in this project - No action needed ## Conclusion The headkit-storefront repository is **not affected** by the React Flight / Next.js RCE advisory because: 1. ✅ Next.js is already at a patched version (16.0.7) 2. ✅ No vulnerable React Flight packages are installed 3. ✅ React and React DOM themselves are not vulnerable to this advisory **No code changes are required.** 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 headkit-storefront. 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