Fix React Server Components RCE vulnerability #7
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 Security Fix SUMMARY: Updated the project to address the React Flight / Next.js RCE advisory. The project was already using Next.js and required a security update. DETECTION RESULTS: ✅ Project is affected by advisory: - Next.js detected at version 16.0.1 (16.x range) - No React Flight packages (react-server-dom-*) found - React versions: 19.2.0 (safe version) CHANGES IMPLEMENTED: Modified: package.json - Updated next from 16.0.1 to 16.0.7 (patched version for 16.x) VERIFICATION: ✓ Dependencies resolved successfully - npm install completed without errors ✓ Lockfile updated correctly - package-lock.json shows next@16.0.7 ✓ No vulnerability warnings in npm audit ✓ All dependent packages (@next/env, @next/swc-*) updated to 16.0.7 BUILD STATUS: The Next.js build compilation completes successfully. There is a pre-existing TypeScript type error in ./app/recipes/[slug]/comments.tsx (unrelated to the security fix) that prevents the full build from completing. This is an application-level issue, not a dependency-related issue, and falls outside the scope of dependency security patching. TECHNICAL NOTES: - The project uses npm as the package manager (package-lock.json) - Only one package.json file found (no monorepo structure) - React and React DOM did not require updates for this Next.js patch - The advisory fix ensures Next.js 16.0.7 includes security patches to prevent RCE vulnerabilities in React Flight / Server Component handling AFFECTED VERSIONS FIXED: - Next.js 16.0.1 → 16.0.7 (includes RCE fix for React Flight/RSC vulnerability) 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.
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 recipes-v2. 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