Fix React Server Components RCE vulnerability - #1
Draft
vercel[bot] wants to merge 1 commit into
Draft
Conversation
React Flight / Next.js RCE Advisory - Assessment Report VULNERABILITY ASSESSMENT ======================= Project Status: ALREADY PATCHED ✓ The project uses Next.js 15.3.6, which is affected by the React Flight / Next.js RCE advisory. FINDINGS: 1. Next.js Version: 15.3.6 - Status: ✓ Already updated to patched version - Required patch: 15.3.x → 15.3.6 - Current version matches requirement 2. React Flight Packages: NOT USED - react-server-dom-webpack: Not found - react-server-dom-parcel: Not found - react-server-dom-turbopack: Not found 3. React Versions: - react: ^18.3.1 (React 18 - not affected, no update needed) - react-dom: ^18.3.1 (React 18 - not affected, no update needed) ACTIONS TAKEN ============= No code changes were required. The project: 1. Already depends on Next.js 15.3.6 (the patched version for 15.3.x) 2. Does not use any vulnerable React Flight packages 3. Does not use vulnerable React 19.0.0/19.1.0/19.1.1/19.2.0 versions VERIFICATION ============ ✓ Build successful: npm run build completed without errors ✓ TypeScript validation: npm run typecheck passed ✓ Lockfile verified: package-lock.json resolves next@15.3.6 correctly ✓ No additional changes needed CONCLUSION ========== The portfolio project is already compliant with the React Flight / Next.js RCE advisory. No package.json modifications, lockfile updates, or patches were necessary. 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 portfolio. 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