Fix React Server Components RCE vulnerability #13
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 repository to address the React Flight / Next.js RCE advisory by upgrading vulnerable Next.js packages to patched versions. ### Project Analysis - **Project Type**: Next.js application - **Affected**: Yes - Next.js 15.0.3 requires patching - **Vulnerable Packages Found**: `next` 15.0.3 - **React Flight Packages**: None detected (no `react-server-dom-*` packages) ### Changes Made #### Files Modified 1. **package.json** - Upgraded `next` from 15.0.3 → 15.0.5 - Upgraded `eslint-config-next` from 15.0.3 → 15.0.5 2. **package-lock.json** - Updated lockfile to resolve Next.js 15.0.5 and all transitive dependencies ### Vulnerability Details The project was using Next.js 15.0.3, which is affected by the React Flight / Next.js RCE advisory. According to the advisory: - Next.js 15.0.x versions < 15.0.5 are vulnerable - The fix applies to all Next.js 15.0.x releases ### Upgrade Logic Applied - Detected Next.js 15.0.3 → Applied 15.0.5 patch (15.0.x → 15.0.5) - Did NOT manually upgrade React/React-DOM (Next.js 15.0.5 supplies the correct patched versions automatically) - Did NOT modify any React Flight packages (none present in project) ### Verification ✅ **Build Status**: Successful - Ran `npm run build` after updating dependencies - Build completed with no dependency-related errors - All pages compiled successfully - Static generation completed for all routes ✅ **Dependency Resolution**: Verified - `npm list next` confirms installation of Next.js 15.0.5 - lockfile.json properly reflects the patched version ### Testing Notes - The project is a Next.js app with React 18.3.1 (not vulnerable versions 19.0.0, 19.1.0, 19.1.1, 19.2.0) - No React Flight packages were present in the project - Only Next.js package required patching - Build verification passed without issues ### Summary of Changes - 2 files modified: package.json, package-lock.json - 0 files created: No new configuration needed - All changes follow the official advisory guidance Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
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.
A critical remote code execution (RCE) vulnerability in React Server Components, impacting frameworks such as Next.js, was identified in the project ai-sdk-preview-pdf-support. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.
This issue is tracked under:
This automated pull request upgrades the affected React and Next.js packages to patched versions that remediate the issue.
More Info