Fix React Server Components RCE vulnerability#54
Draft
vercel[bot] wants to merge 4 commits intomainfrom
Draft
Conversation
## React Flight / Next.js RCE Advisory - Security Update
### Summary
Successfully addressed the React Flight / Next.js RCE advisory for the aether-ui project by upgrading Next.js to the patched version.
### Detection Results
- **Project Type:** Single Next.js application with TypeScript
- **Package Manager:** pnpm (v9.15.4)
- **Affected Dependencies Found:**
- ✅ next@15.2.4 (VULNERABLE - detected)
- ✅ @next/mdx@15.2.4 (VULNERABLE - detected)
- ✅ eslint-config-next@15.2.4 (VULNERABLE - detected)
- **React Flight Packages:** None detected (project does not use react-server-dom-* packages)
- **React/React-DOM:** ^18.3.1 (NOT affected - using React 18, not the vulnerable React 19 versions)
### Changes Made
#### Files Modified
1. **package.json**
- `next`: 15.2.4 → 15.2.6 (patched version for 15.2.x minor)
- `@next/mdx`: 15.2.4 → 15.2.6 (patched version)
- `eslint-config-next`: 15.2.4 → 15.2.6 (patched version)
- No manual changes to react or react-dom (as per advisory recommendations)
2. **pnpm-lock.yaml**
- Updated to reflect patched versions of all Next.js packages
- Final resolved versions:
- next@15.2.6 ✅
- eslint-config-next@15.2.6 ✅
- @next/mdx@15.5.7 (compatible resolution from ^15.2.6 spec)
- react@18.3.1 (unchanged - as required)
- react-dom@18.3.1 (unchanged - as required)
### Testing & Verification
#### Installation
- ✅ `pnpm install` completed successfully
- ✅ All 554 dependencies resolved correctly
- ✅ No installation conflicts or resolution errors
#### Build Verification
- ✅ `pnpm build` completed successfully using Next.js 15.2.6
- ✅ All 22 static pages generated successfully
- ✅ No build errors or warnings related to the version upgrade
- ✅ Production build optimized and finalized
#### Linting
- ✅ `pnpm lint` executed successfully
- ✅ Only pre-existing warnings present (not related to security update)
- ✅ No new errors introduced
### Security Impact
This update addresses a critical RCE vulnerability in Next.js that could be exploited through React Flight / Server Components. By upgrading to 15.2.6:
- Patches the vulnerability in Next.js's handling of React Flight serialization
- Maintains compatibility with existing React 18.3.1 dependencies
- Ensures the application is no longer vulnerable to the advisory
### Implementation Notes
- Followed the official upgrade path for Next.js 15.2.x (→ 15.2.6)
- Did not upgrade across major versions as per advisory guidance
- Did not manually modify react or react-dom versions (Next.js manages these automatically)
- Project does not use React Flight packages directly, so no additional react-server-dom-* updates were needed
- All package manager operations completed successfully with pnpm
### Files Changed Summary
- Modified: package.json
- Modified: pnpm-lock.yaml
- Created: .vade-report
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Owner
pantharshit007
left a comment
pantharshit007
left a comment
There was a problem hiding this comment.
this PR wouldn't be approved as its directly a branch from prod instead of main I will update the vulnerability myself.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 aether-ui. 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