Skip to content

Conversation

@vercel
Copy link
Contributor

@vercel vercel bot commented Dec 8, 2025

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 on-demand-isr. 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 | [email protected]

## React Flight / Next.js RCE Advisory Security Patch

### Summary
Successfully updated the on-demand-isr repository to address the React Flight / Next.js RCE advisory by upgrading Next.js to a patched version.

### Changes Made

#### Detection
- Analyzed `package.json` and identified the project uses:
  - `next` (affected - version 15.3.0-canary.15)
  - `react` and `react-dom` (not vulnerable by themselves)
  - No React Server Components/Flight packages (`react-server-dom-*`)

#### Vulnerability Assessment
- The project uses Next.js 15.3.x, which is in the affected minor version range
- Applied the patching rule for Next.js 15.3.x → 15.3.6

#### Files Modified
1. **package.json**
   - Upgraded `next` from `15.3.0-canary.15` to `15.3.6`
   - Note: `react` and `react-dom` remain at `^19.0.0` (Next.js supplies patched versions automatically)

2. **pnpm-lock.yaml**
   - Updated lockfile to resolve `[email protected]`
   - Verified the lockfile contains exact patched version: `[email protected]`
   - All dependencies resolved correctly

### Build Verification
- TypeScript compilation: ✅ Passed (no type errors)
- Next.js compilation: ✅ Passed ("Compiled successfully")
- Build failure due to missing environment variables (GITHUB_APP_ID, GITHUB_APP_PK_PEM) is unrelated to the security patch
- This is expected application configuration, not a dependency issue

### Implementation Details
- Followed the official upgrade rules for Next.js 15.3.x
- Did not manually upgrade React dependencies (Next.js handles this automatically)
- Ran `pnpm install` to update lockfile and ensure dependency resolution
- Verified patched versions are correctly resolved in the lockfile

### Security Impact
The upgrade to Next.js 15.3.6 patches the React Flight / Server Components RCE vulnerability by addressing the underlying issues in Next.js that could allow arbitrary code execution.

### No Breaking Changes
- The upgrade is within the same minor version (15.3.x)
- No manual code changes required
- Existing functionality preserved

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

vercel bot commented Dec 8, 2025

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

Project Deployment Preview Comments Updated (UTC)
on-demand-isr Ready Ready Preview Comment Dec 8, 2025 9:34pm

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednext@​15.3.0-canary.15 ⏵ 15.3.683 +185 +6091 +19870

View full report

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