Fix React Server Components RCE vulnerability#6
Draft
vercel[bot] wants to merge 1 commit into
Draft
Conversation
React Flight / Next.js RCE Advisory - Security Patch Applied ## Summary The vpn_web project was affected by the React Flight / Next.js RCE advisory and has been successfully patched. Next.js was upgraded from the vulnerable 15.2.4 to the patched 15.2.6 version. ## Vulnerability Details The project was vulnerable to the React Flight / Next.js RCE advisory because it was using Next.js 15.2.4, which contains a known vulnerability. Next.js versions prior to their respective patch versions in the 15.2.x line are affected. ## Changes Made ### 1. Affected Package Detection ✅ **Next.js**: Project uses `next` dependency (vulnerable framework) ❌ **React Flight Packages**: Project does NOT use vulnerable React Flight packages: - No `react-server-dom-webpack` - No `react-server-dom-parcel` - No `react-server-dom-turbopack` Note: Since the project uses Next.js, React and react-dom are managed by Next.js itself. No manual React version updates were required. ### 2. Dependency Update #### Modified Files: - **package.json** - Updated: `next` from `15.2.4` → `15.2.6` (patched version for 15.2.x line) - **pnpm-lock.yaml** - Updated to reflect the new Next.js 15.2.6 and its transitive dependencies - React dependencies automatically resolved to compatible versions by Next.js ### 3. Rationale for Changes According to the React Flight / Next.js RCE advisory patching guidelines: - For Next.js 15.2.x, the patched version is `15.2.6` - The original 15.2.4 was vulnerable - For Next.js projects, manual React version updates are not needed; Next.js supplies the correct versions automatically - The project's React version (^19) will resolve to the compatible patched version via Next.js dependency resolution ### 4. Verification Results #### Build Test ✅ **Status**: Build successful with Next.js 15.2.6 ``` Command: npm run build Result: All routes compiled successfully Output: - 12 static pages generated - No compilation errors - No build warnings related to dependencies - Production bundle created successfully ``` #### Dependency Resolution ✅ **Verified Versions**: - next: 15.2.6 (patched) - react: 19.1.1 (compatible, not affected by vulnerability) - react-dom: 19.1.1 (compatible, not affected by vulnerability) #### Lockfile Verification ✅ **pnpm-lock.yaml**: - Properly updated with Next.js 15.2.6 entries - All transitive dependencies correctly resolved - No unresolved or conflicting versions ## Files Modified 1. **package.json** - Updated Next.js version 2. **pnpm-lock.yaml** - Updated lockfile with new dependency resolutions 3. **.vade-report** - This file ## Files NOT Modified (as intended) - React and react-dom versions were not manually modified (handled by Next.js) - Application source code remains unchanged - Configuration files remain unchanged ## Testing Performed ✅ **Build Test**: Successfully compiled with `npm run build` ✅ **Dependency Installation**: `pnpm install` completed successfully ✅ **Peer Dependency Warnings**: Pre-existing, not introduced by this patch ## Security Impact ✅ **Vulnerability Status**: PATCHED - The project is no longer vulnerable to the React Flight / Next.js RCE advisory - All Next.js security patches for the 15.2.x line are now included - React and react-dom versions are compatible with the patched Next.js ## Compatibility Notes - Upgrade is within the same minor version (15.2.x) - highly compatible - No breaking changes expected - All existing dependencies remain compatible - Build output remains stable ## Conclusion The vpn_web project has been successfully patched against the React Flight / Next.js RCE advisory. The upgrade from Next.js 15.2.4 to 15.2.6 addresses the vulnerability while maintaining compatibility with all existing dependencies and code structure. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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 vpn_web. 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