Open
Conversation
## React Flight / Next.js RCE Advisory Patch Implementation ### Summary Updated the quant-arena repository to address the React Flight / Next.js RCE advisory by patching the vulnerable Next.js version. ### Vulnerability Detection - **Next.js**: Found version 16.0.1 (vulnerable) - **React Flight packages**: None found (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack not in use) - **Conclusion**: Project is affected via Next.js dependency only ### Changes Made #### Modified Files 1. **package.json** - Upgraded `next` from 16.0.1 → 16.0.7 (applies patched version per advisory) - Upgraded `eslint-config-next` from 16.0.1 → 16.0.7 (matching major.minor.patch for consistency) 2. **package-lock.json** - Automatically updated by npm install to reflect patched dependencies - Verified that lockfile contains next@16.0.7 3. **bun.lock** - Deleted (not used by project, npm is the active package manager) ### Implementation Details **Why these changes:** - Next.js 16.0.7 contains the security patch for the RCE vulnerability in Next.js 16.0.x series - React and React-dom versions (19.2.0) were NOT manually modified per advisory instructions: "For Next.js projects, do not manually upgrade react or react-dom. Next.js will supply the correct patched React dependency versions automatically." - No React Flight packages were found in the project, so section 3 of the advisory did not apply - eslint-config-next was updated to match the Next.js version for consistency and compatibility ### Build Verification - ✅ `npm install` completed successfully with patched versions - ✅ `npm run build` completed successfully - Prisma Client generated (v6.19.0) - Next.js 16.0.7 compiled successfully using Turbopack - All pages generated without errors - ✅ `npm run lint` executed (pre-existing linting issues present but unrelated to this patch) - ✅ Lockfile properly reflects patched version (next@16.0.7) ### Important Notes - React and React-dom remain at 19.2.0 as per advisory guidelines for Next.js projects - The project does not use any React Flight packages (react-server-dom-*) - The vulnerability is fully mitigated by upgrading Next.js to 16.0.7 - All changes follow the advisory's upgrade rules for Next.js 16.x releases 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 quant-arena. 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