Fix React Server Components RCE vulnerability #109
+420
−750
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 - Vulnerability Fix
SUMMARY:
This repository was assessed for the React Flight / Next.js RCE advisory and patched where affected.
VULNERABILITY DETECTION:
✅ Project is affected by the advisory
Found the following vulnerable packages:
- next@16.0.3 in apps/nextjs/package.json (via "latest" specifier)
- next@14.0.4 in packages/web/package.json (devDependency)
OTHER PACKAGES CHECKED:
- apps/astro: Not vulnerable (no Next.js or React Flight packages)
- apps/nuxt: Not vulnerable (no Next.js or React Flight packages)
- apps/remix: Not vulnerable (no Next.js or React Flight packages)
- apps/sveltekit: Not vulnerable (no Next.js or React Flight packages)
- apps/vue: Not vulnerable (no Next.js or React Flight packages)
- Root package.json: Not vulnerable (no Next.js or React Flight packages)
CHANGES MADE:
1. Modified: apps/nextjs/package.json
- Updated "next": "latest" → "next": "16.0.7"
- Reason: Upgraded Next.js 16.x to patched version 16.0.7 to address RCE vulnerability
2. No changes to packages/web/package.json
- Reason: next@14.0.4 doesn't match any of the upgrade rules specified:
- Rules only cover 14.3.0-canary.77+ (downgrade to canary.76)
- Rules don't cover 14.0.x stable releases
- To maintain stability, only versions explicitly listed were updated
3. Updated: pnpm-lock.yaml
- Resolved next@16.0.7 and all its transitive dependencies
- React/React-DOM automatically updated to compatible patched versions by Next.js
- All other dependencies resolved correctly
VERIFICATION:
✅ Dependencies installed successfully with `pnpm install`
✅ Build verification passed for apps/nextjs with `pnpm build`
- Next.js 16.0.7 compiled successfully
- All static pages generated without errors
- TypeScript type checking passed
✅ Lockfile properly reflects patched versions
- next@16.0.7 present in apps/nextjs section of pnpm-lock.yaml
- React and React-DOM automatically aligned to 19.2.1 (compatible with patched Next.js)
NOTES:
- The "latest" specifier in apps/nextjs/package.json has been pinned to 16.0.7 for security and stability
- React and React-DOM in apps/nextjs remain at "latest" as per the advisory guidance (Next.js manages React versions automatically)
- No React Flight packages (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack) were found in the monorepo, so section 3 of the advisory did not apply
- The peer dependency warning for @playwright/test@^1.51.1 (but installed 1.49.0) is pre-existing and not related to this security fix
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 speed-insights-nextjs. 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