Fix React Server Components RCE vulnerability #29
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 Fix ## Summary Updated the repository to address the React Flight / Next.js RCE advisory by upgrading Next.js to a patched version. ## Analysis Scanned all workspace package.json files to identify affected packages: - **apps/website/package.json**: Contains `next@16.0.3` (VULNERABLE) - **apps/app/package.json**: Does not use Next.js or React Flight packages - **packages/agent-cli-sdk/package.json**: No Next.js or React Flight packages - **packages/agentcmd-workflows/package.json**: No Next.js or React Flight packages No React Flight packages (`react-server-dom-webpack`, `react-server-dom-parcel`, `react-server-dom-turbopack`) were found in the project. ## Changes Made ### Modified Files - **apps/website/package.json**: Upgraded `next` from `16.0.3` to `16.0.7` - React and React DOM were not modified as they are already at safe versions (19.2.0) - Next.js version 16.0.7 includes the security fix for the RCE vulnerability ### Updated Lockfiles - **pnpm-lock.yaml**: Updated to reflect the new Next.js 16.0.7 dependency and all transitive dependencies ## Verification ✅ Successfully ran `pnpm install` to update lockfiles ✅ Verified that `next@16.0.7` is correctly resolved in pnpm-lock.yaml ✅ Successfully built the website app with `pnpm build` to confirm no regressions ## Implementation Details - Only the affected package (Next.js in the website app) was upgraded to the patched version - No changes were made to React or React DOM as per the advisory instructions (Next.js handles these automatically) - All peer dependency warnings are pre-existing and unrelated to this fix - The build completed successfully with no errors ## Security Impact The upgrade from Next.js 16.0.3 to 16.0.7 addresses the React Flight / Next.js RCE advisory by including security patches that prevent remote code execution attacks through the React Flight protocol. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Contributor
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 agentcmd-website. 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