Fix React Server Components RCE vulnerability #117
Merged
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 Patch Project: devb.io (www) Package Manager: pnpm@10.11.0 VULNERABILITY ASSESSMENT ======================== Detection Result: VULNERABLE The project uses a vulnerable version of Next.js in a canary release that contains the React Flight / Next.js RCE vulnerability. Vulnerable Package Identified: - next: 15.2.0-canary.69 (canary versions >= 14.3.0-canary.77 are vulnerable) - eslint-config-next: 15.2.0-canary.69 Vulnerability Details: - CVE/Advisory: React Flight / Next.js RCE vulnerability affecting React Server Components - Affected Version: 15.2.0-canary.69 - Patched Version Required: 15.2.6 (per Next.js 15.2.x advisory specifications) REMEDIATION APPLIED ==================== 1. Package Updates: ✓ Upgraded next: 15.2.0-canary.69 → 15.2.6 ✓ Upgraded eslint-config-next: 15.2.0-canary.69 → 15.2.6 2. Files Modified: ✓ www/package.json - Updated next and eslint-config-next versions ✓ www/pnpm-lock.yaml - Updated lockfile with patched versions 3. Dependency Installation: ✓ Ran `pnpm install` to resolve and lock patched versions ✓ All dependencies resolved correctly ✓ No compatibility issues detected 4. Build Verification: ✓ Production build completed successfully: `npm run build` ✓ Build output confirms Next.js 15.2.6 is active ✓ No errors or breaking changes introduced ✓ Existing linting warnings are unrelated to security patch React Version Notes: - Current: react@^19.0.0 and react-dom@^19.0.0 - Action: No manual React version update required - Reason: Next.js 15.2.6 manages React compatibility internally - Status: React versions are compatible with Next.js 15.2.6 VERIFICATION CHECKLIST ====================== ✓ Vulnerability Detection: Project uses vulnerable Next.js canary version ✓ Advisory Compliance: Updated to patched version 15.2.6 per guidelines ✓ Build Success: Production build completes without errors ✓ Lockfile Updated: pnpm-lock.yaml resolves to patched versions ✓ No Regressions: Application builds and runs correctly ✓ React Not Manually Patched: Following Next.js best practices SECURITY STATUS =============== Before Patch: VULNERABLE After Patch: SECURE The project is now protected against the React Flight / Next.js RCE vulnerability. Next.js 15.2.6 includes all necessary security fixes for React Server Components. No further action required. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Contributor
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 devb-io. 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