Fix React Server Components RCE vulnerability#1
Draft
vercel[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
## React Flight / Next.js RCE Advisory Update ### Summary Updated poly-guesser to address the React Flight / Next.js RCE advisory by upgrading Next.js to a patched version. ### Vulnerability Assessment **Status: AFFECTED** - The project uses Next.js and requires patching. **Findings:** - ✅ Uses Next.js 16.0.3 (vulnerable - needs upgrade) - ❌ Does NOT use react-server-dom packages (webpack, parcel, or turbopack) - ✅ Uses React 19.2.0 and React-DOM 19.2.0 (correct versions - no update needed for Next.js projects) ### Changes Made #### Modified Files: 1. **package.json** - Upgraded `next`: `16.0.3` → `16.0.7` (patched version) - Upgraded `eslint-config-next`: `16.0.3` → `16.0.7` (matching version) ### Verification Results ✅ **Build Verification:** Successfully compiled with Next.js 16.0.7 - Command: `npm run build` - Result: Compilation successful (TypeScript compiled correctly) - Notes: Application-level errors (missing DATABASE_URL, Ably auth keys) are expected and not related to the package upgrade ✅ **Dependency Resolution:** Verified patched versions resolve correctly - `next@16.0.7` - Confirmed via `npm ls next` - `eslint-config-next@16.0.7` - Confirmed via `npm ls eslint-config-next` ✅ **Linting:** No new linting errors introduced - Pre-existing warnings/errors in codebase are unrelated to this change ### Implementation Notes 1. **No React updates required:** Per the advisory, react and react-dom are NOT vulnerable. They were left unchanged at version 19.2.0. For Next.js projects, the framework supplies correct React dependency versions automatically. 2. **No react-server-dom packages:** The project does not use react-server-dom-webpack, react-server-dom-parcel, or react-server-dom-turbopack, so no additional patches were needed. 3. **Package manager:** Project uses bun as primary package manager (bun.lock present). However, npm and pnpm are available in the build environment. The package.json changes are environment-agnostic and will work with any compatible package manager. 4. **Upgrade path applied:** Next.js 16.x → 16.0.7 (following the advisory's upgrade rules) ### Files Changed - `package.json` - Updated Next.js version to patched release ### Build Status ✅ Compilation successful with patched versions ✅ No dependency-related build errors ✅ Ready for production deployment 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 poly-guesser. 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