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 Patch Implementation
PROJECT STATUS: PATCHED - Changes Applied
SUMMARY:
This project was assessed for vulnerability to the React Flight / Next.js RCE advisory and patched accordingly.
ANALYSIS:
1. Affected Package Detection:
✓ Project uses Next.js: YES (version 15.2.6)
✓ Project uses React Flight packages: NO
- No react-server-dom-webpack
- No react-server-dom-parcel
- No react-server-dom-turbopack
2. Vulnerability Assessment:
The React Flight RCE vulnerability affects applications using Next.js and/or React Server
Components packages. While the project uses Next.js, the vulnerability is most severe when
combined with React Flight packages. This Next.js project has been patched to the latest
secure version for its minor release.
3. Changes Applied:
Package.json modifications:
- Updated "next" from 15.2.4 to 15.2.6 (patched version for 15.2.x)
- Updated "@next/third-parties" from 15.4.2 to 15.2.6 (aligned with Next.js version)
Current Versions:
- Next.js: 15.2.6 (✓ patched version for 15.2.x)
- @next/third-parties: 15.2.6 (aligned with Next.js)
- React: ^19 (latest patch version via package manager)
- React-dom: ^19 (latest patch version via package manager)
4. Lockfile Updates:
- pnpm-lock.yaml: Updated to reflect Next.js 15.2.6 and all resolved dependencies
- Build verified with updated dependencies
5. Verification:
✓ Build succeeds: "npm run build" completed successfully
✓ Linting: No errors introduced
✓ All static pages generated correctly (15/15)
✓ No dependency conflicts or resolution issues
CONCLUSION:
The project has been successfully patched to address the React Flight / Next.js RCE advisory.
The Next.js version is now at the patched version (15.2.6) for the 15.2.x minor release, and
the build verifies all changes are working correctly.
FILES MODIFIED:
- package.json (Next.js version upgrade)
- pnpm-lock.yaml (dependency lock file updated)
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 shadowctrl. 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