Fix React Server Components RCE vulnerability#556
Draft
vercel[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
# React Flight / Next.js RCE Advisory Remediation Report ## Summary After thorough analysis of the ouorz-mono monorepo, **necessary vulnerability patches have been applied**. The project was partially vulnerable to the React Flight / Next.js RCE vulnerabilities (CVE-2025-55182 and CVE-2025-66478) and has been remediated. ## Vulnerability Detection Results ### Affected Next.js Versions Identified The project contains Next.js applications with potentially vulnerable versions: - **apps/main**: next@16.0.5 → VULNERABLE (requires patch 16.0.7) - **apps/preview**: next@15.1.0 → VULNERABLE (requires patch 15.1.9) ### Not Vulnerable (No Action Required) - **apps/interface**: next@13.4.3 → Not in vulnerable range - **apps/analytics**: next@14.0.3 → Not affected (stable 14.0.x not vulnerable) ### React Flight Packages **Finding:** The project does NOT use any React Flight packages: - No `react-server-dom-webpack` - No `react-server-dom-parcel` - No `react-server-dom-turbopack` While React 19.0.0 is resolved in @ouorz/preview, the vulnerability is specific to react-server-dom-* packages, not React itself. ## Changes Applied ### 1. apps/main/package.json - Updated `next` from `^16.0.5` to `^16.0.7` - **Reason**: Next.js 16.0.5 is vulnerable to CVE-2025-66478. Version 16.0.7 is the patched release for the 16.x series. ### 2. apps/preview/package.json - Updated `next` from `15.1.0` to `15.1.9` - **Reason**: Next.js 15.1.0 is vulnerable to CVE-2025-66478. Version 15.1.9 is the patched release for the 15.1.x series. ### 3. pnpm-lock.yaml - Updated lockfile to reflect new Next.js versions and their dependencies - Verified that all transitive dependencies resolve correctly with patched versions ## Vulnerability Analysis Details ### CVE-2025-66478 (Next.js RCE) **Affected versions:** - Next.js 15.x (all versions) - Next.js 16.x (all versions prior to 16.0.7) - Next.js 14.3.0-canary.77+ (canary releases only) **Root cause:** Vulnerability in React Server Components implementation **Impact:** Remote Code Execution when using App Router **Patched versions applied:** - next@16.0.7 for 16.x series - next@15.1.9 for 15.1.x series - next@13.4.3 and next@14.0.3 are not affected ### CVE-2025-55182 (React Flight RCE) **Affected packages:** react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack in React 19.0.0, 19.1.0, 19.1.1, 19.2.0 **Status:** Not applicable to this project (no react-server-dom-* packages used) ## Files Modified - `apps/main/package.json` - Next.js version bump - `apps/preview/package.json` - Next.js version bump - `pnpm-lock.yaml` - Lockfile update with patched dependency tree ## Files Not Modified - Root `package.json` - No Next.js dependency - `apps/interface/package.json` - Not vulnerable version (13.4.3) - `apps/analytics/package.json` - Not vulnerable version (14.0.3) - React/React-DOM versions - Following Next.js advisory guidance to let Next.js manage React versions - Utility packages - No direct vulnerability ## Build Verification The lockfile changes ensure that: - All Next.js patches are properly resolved - Dependency tree is consistent across the monorepo - No conflicting version constraints ## Verification Steps Performed ✓ Identified all package.json files in monorepo (8 total) ✓ Scanned for vulnerable Next.js versions ✓ Checked for React Flight package usage ✓ Confirmed no react-server-dom-* packages present ✓ Applied appropriate patches per advisory guidelines ✓ Updated pnpm lockfile with patched versions ✓ Verified version constraints resolve correctly ## Advisory Compliance Changes made in accordance with official guidance: - ✓ Next.js versions upgraded to minimum patched versions for their series - ✓ React/React-DOM not manually upgraded (Next.js manages these) - ✓ Only affected packages updated; unaffected versions left unchanged - ✓ Lockfile updated to ensure consistent resolution - ✓ No breaking changes to application code ## Project Impact - Fixes critical RCE vulnerability in affected Next.js versions - Maintains compatibility with existing code (patch updates only) - Monorepo remains functional with improved security posture Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for ouorz-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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 ouorz-main. 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