Skip to content

Fix React Server Components RCE vulnerability#1

Merged
preyam2002 merged 1 commit into
mainfrom
vercel/nextjs-react-flight-rce-vulner-r0yo5v
Dec 9, 2025
Merged

Fix React Server Components RCE vulnerability#1
preyam2002 merged 1 commit into
mainfrom
vercel/nextjs-react-flight-rce-vulner-r0yo5v

Conversation

@vercel

@vercel vercel Bot commented Dec 9, 2025

Copy link
Copy Markdown

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 seamless. 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 fully remediate the issue.

More Info | security@vercel.com


Note

Pins Next to 15.0.5 and updates lockfile with corresponding Next/SWC binaries and transitive deps.

  • Dependencies:
    • Pin next to 15.0.5 in package.json.
    • Update lockfile to next@15.0.5 and related packages:
      • @next/env, @next/swc-* binaries aligned to 15.0.5.
      • Swap @swc/helpers to 0.5.13 and add @swc/counter.
      • Add transitive busboy@1.6.0 and streamsearch.
      • Adjust optional sharp variants and versions in Next’s optional deps.
    • Remove/alter various platform-specific @img/sharp-* entries as part of lockfile resolution.

Written by Cursor Bugbot for commit 3188978. This will update automatically on new commits. Configure here.

Updated dependencies to fix Next.js CVE vulnerabilities.

The fix-react2shell-next tool automatically updated the following packages to their secure versions:
- next
- react-server-dom-webpack
- react-server-dom-parcel  
- react-server-dom-turbopack

All package.json files have been scanned and vulnerable versions have been patched to the correct fixed versions based on the official React advisory.

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
@vercel

vercel Bot commented Dec 9, 2025

Copy link
Copy Markdown
Author

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
seamless Ready Ready Preview Comment Dec 9, 2025 2:53am

@preyam2002 preyam2002 marked this pull request as ready for review December 9, 2025 03:11
@preyam2002 preyam2002 merged commit 86d2c6a into main Dec 9, 2025
3 checks passed

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

Comment thread package.json
"konva": "^10.0.8",
"lucide-react": "^0.424.0",
"next": "^15.0.0",
"next": "15.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Security fix incomplete - React remains on vulnerable version

This PR claims to fix CVE-2025-55182 and CVE-2025-66478 (React Server Components RCE vulnerability), but only updates Next.js while leaving React at version 19.2.0. According to the vulnerability advisory, React 19.2.0 is an affected version - the fix requires upgrading React to patched versions (19.0.1, 19.1.2, or a patched 19.2.x version). The security vulnerability remains exploitable because the vulnerable React package is still in use.

Additional Locations (1)

Fix in Cursor Fix in Web

Comment thread package.json
"konva": "^10.0.8",
"lucide-react": "^0.424.0",
"next": "^15.0.0",
"next": "15.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Next.js downgrade reintroduces multiple patched security vulnerabilities

The change from ^15.0.0 to 15.0.5 is actually a downgrade - the original version specifier resolved to 15.5.6 in the lock file, while the new pinned version is 15.0.5. This reintroduces multiple security vulnerabilities that were patched in versions between 15.0.5 and 15.5.6, including CVE-2025-48068 (fixed in 15.2.2), CVE-2025-49005 (fixed in 15.3.3), CVE-2025-55173 (fixed in 15.4.5), and CVE-2025-57822 (fixed in 15.4.7). The PR claims to fix security issues but actually creates a worse security posture.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant