Skip to content

Conversation

@vercel
Copy link

@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 action-g. 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

React Flight / Next.js RCE Advisory - Security Patch Applied

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

## Vulnerability Detection
✓ **Project IS affected**: Uses Next.js 16.0.1 (vulnerable version)
✗ **No React Flight packages**: The project does not use react-server-dom-webpack, react-server-dom-parcel, or react-server-dom-turbopack
✓ **React version**: Already on React 19.2.0 (no manual update needed)

## Changes Made

### Modified Files:
- **package.json**: 
  - Upgraded `next` from 16.0.1 → 16.0.7 (patched version for 16.x)
  - Upgraded `eslint-config-next` from 16.0.1 → 16.0.7 (matching Next.js version)

### Lockfile Updates:
- **package-lock.json**: Updated with Next.js 16.0.7 and all transitive dependencies
- Next.js and all platform-specific binaries (@next/swc-*) are now pinned to 16.0.7

## Verification

### Build Status:
✓ **Successful**: `npm run build` completes without errors
  - Next.js 16.0.7 (Turbopack) compiled successfully
  - All static pages generated correctly
  - TypeScript compilation passed

### Dependency Status:
✓ **Lockfile verified**: package-lock.json correctly resolves Next.js 16.0.7
✓ **No React Flight dependencies**: Project does not require React Flight packages
✓ **React versions**: Automatic Next.js management (no manual override needed)

## Implementation Notes

1. **Package Manager**: Project uses npm (primary) with bun.lock also present
2. **Next.js Version Strategy**: Since next@16.x was affected, upgraded to 16.0.7 per the advisory
3. **React Versions**: No manual React version changes needed - Next.js 16.0.7 provides compatible React 19.2.0
4. **No Breaking Changes**: The upgrade to 16.0.7 is a patch release with backward compatibility

## Security Impact
The project is now protected against the React Flight / Next.js RCE vulnerability identified in the advisory. The patched Next.js 16.0.7 version resolves the security issue while maintaining full compatibility with the existing codebase.

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
@vercel
Copy link
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)
action-g Ready Ready Preview Comment Dec 8, 2025 5:15pm

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.

0 participants