Fix React Server Components RCE vulnerability #499
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 Mitigation ### Summary Successfully updated the code-graph repository to address the React Flight / Next.js RCE advisory by upgrading to the latest patched version of Next.js. ### Vulnerability Detection The project was identified as affected because: - ✅ Uses Next.js version 15.1.2 (vulnerable, within 15.1.x range) - ❌ Does NOT use React Flight packages (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack) - Uses React 18 (not directly vulnerable, but needs patched Next.js) ### Changes Made #### Modified Files 1. **package.json** - Upgraded `next` from `^15.1.2` to `15.1.9` (exact version) - Upgraded `eslint-config-next` from `^15.1.2` to `15.1.9` (exact version) - Left `react` and `react-dom` unchanged as per Next.js guidelines (Next.js handles React dependencies) #### Updated Lockfile 1. **package-lock.json** - Regenerated lockfile with `npm install` after upgrading dependencies - Verified exact version 15.1.9 resolved for Next.js ### Verification Results ✅ **Build Verification**: `npm run build` completed successfully - Next.js 15.1.9 confirmed in output - All 6 routes compiled without errors - Build time: acceptable ✅ **Linter Verification**: `npm run lint` passed - No new errors introduced - Pre-existing React Hook warnings are unrelated to this change ✅ **Lockfile Verification**: Package-lock.json contains exact patched version - next: 15.1.9 ✓ ### Implementation Notes - Used exact version specifications (removed caret ranges) to ensure 15.1.9 is installed, not a newer minor version - No code changes were required, only dependency version bumps - No React Flight packages were present, so only Next.js upgrade was needed - React dependencies remain at ^18, as Next.js 15.1.9 maintains compatibility ### Testing Summary - Build: ✅ PASSED - Lint: ✅ PASSED - No test scripts exist in package.json, so no further testing available This change ensures the code-graph project is protected against the React Flight RCE vulnerability while maintaining full compatibility with existing code. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
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 code-graph. 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