Fix React Server Components RCE vulnerability #418
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 Scan - React Flight / Next.js RCE Security Fix ## Summary Updated the react-scan monorepo to address the React Flight / Next.js RCE advisory by upgrading the vulnerable Next.js dependency. ## Analysis Scanned all package.json files in the monorepo: - Root package.json: No Next.js or React Flight packages found ✓ - kitchen-sink/package.json: React 19.0.0, React-DOM 19.0.0 (Vite app, no Next.js) ✓ - packages/extension/package.json: React 18.2.0 (React Scan extension, no Next.js) ✓ - packages/scan/package.json: No React Flight packages ✓ - packages/vite-plugin-react-scan/package.json: No React Flight packages ✓ - packages/website/package.json: **Next.js 15.2.1 VULNERABLE**⚠️ ## Changes Made ### Modified Files 1. **packages/website/package.json** - Upgraded `next` from `15.2.1` to `15.2.6` (patched version for 15.2.x series) - React and React-DOM were NOT manually updated as Next.js supplies correct patched versions automatically 2. **pnpm-lock.yaml** - Updated lockfile by running `pnpm install` - Verified that `[email protected]` is now resolved in the lockfile ## Vulnerability Details - **Advisory**: React Flight / Next.js RCE vulnerability - **Affected Version**: Next.js 15.2.1 - **Patched Version**: Next.js 15.2.6 - **Rule Applied**: For Next.js 15.2.x -> upgrade to 15.2.6 ## Verification ✓ Dependencies installed successfully with `pnpm install` ✓ Build verified: `next build` completed successfully ✓ No build errors or dependency conflicts ✓ Output confirmed: "Compiled successfully" ## No Changes Required For - React Flight packages: Project does not use `react-server-dom-webpack`, `react-server-dom-parcel`, or `react-server-dom-turbopack` - Other workspaces: None contained vulnerable Next.js versions ## Files Staged - packages/website/package.json - pnpm-lock.yaml - .vade-report Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
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 react-scan. 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 | [email protected]