Fix React Server Components RCE vulnerability #2
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 project to address the React Flight / Next.js RCE advisory as requested. ## Project Status ✓ AFFECTED: Project uses Next.js 16.0.1 ✗ NOT AFFECTED BY REACT FLIGHT: Project does not use react-server-dom-webpack, react-server-dom-parcel, or react-server-dom-turbopack ## Changes Implemented ### Modified Files: 1. **package.json** - Updated `next` from `16.0.1` to `16.0.7` (patched version for 16.x) - No changes to React or React DOM versions (Next.js handles these automatically) 2. **pnpm-lock.yaml** - Automatically updated during `pnpm install` to reflect next@16.0.7 - Verified that lockfile now resolves to next@16.0.7 ## Implementation Details According to the advisory: - Next.js 16.x versions should be patched to 16.0.7 - The project did not use any React Flight packages (react-server-dom-*), so only Next.js required patching - React (19.2.0) and React DOM (19.2.0) remain unchanged as they are not directly vulnerable and Next.js will provide the correct versions automatically ## Verification ✓ **Build Verification**: `npm run build` completed successfully - Next.js 16.0.7 (Turbopack) built the project without errors - All 52 static pages generated successfully - No dependency-related errors ✓ **Lockfile Verification**: Confirmed that pnpm-lock.yaml contains next@16.0.7 - Dependencies installed cleanly with pnpm v9.15.9 - No unresolved dependency conflicts ✓ **No Regressions**: Build output shows all routes processed correctly ## Notes - The project uses pnpm as its package manager (pnpm@9.15.9+sha512...) - ESLint configuration warning in next.config.mjs is pre-existing and unrelated to this security update - No test suite present in the project (no test/spec scripts configured) 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 v0-workflow-registry. 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