Fix React Server Components RCE vulnerability - #2
Conversation
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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
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.
| "@next/swc-linux-x64-gnu": "15.2.5", | ||
| "@next/swc-linux-x64-musl": "15.2.5", | ||
| "@next/swc-win32-arm64-msvc": "15.2.5", | ||
| "@next/swc-win32-x64-msvc": "15.2.5", |
There was a problem hiding this comment.
Bug: Mismatched Next.js SWC binary versions in lockfile
The next package is upgraded to version 15.2.6 and @next/env is at 15.2.6, but all @next/swc-* binary packages are locked to version 15.2.5. This version mismatch in the lockfile may result in incompatible binaries being used or potentially incomplete security patches if the fix spans both the main package and the SWC compilation binaries. The optional dependencies explicitly specify 15.2.5 while the main package is 15.2.6.
Additional Locations (1)
| "clsx": "^2.1.1", | ||
| "lucide-react": "^0.460.0", | ||
| "next": "^15.2.4", | ||
| "next": "15.2.6", |
There was a problem hiding this comment.
Bug: React packages not upgraded despite PR claiming fix
The PR description explicitly states it "upgrades the affected React and Next.js packages to patched versions" and references React Advisory CVE-2025-55182, but the diff shows only Next.js being upgraded while react and react-dom remain unchanged at ^19.0.0. If the React vulnerability requires a specific patched React version, the security fix may be incomplete, potentially leaving the application vulnerable to the RCE attack vector described in the advisory.
1 participant
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
Note
Bumps
nextto15.2.6(pinning version) and updates related@next/envand platform-specific@next/swc-*packages in the lockfile.nextfrom^15.2.4to15.2.6inpackage.json(remove caret to pin).@next/envto15.2.6and platform-specific@next/swc-*binaries to15.2.5inpackage-lock.json.Written by Cursor Bugbot for commit 9391a59. This will update automatically on new commits. Configure here.