Fix React Server Components RCE vulnerability#7
Draft
vercel[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
## React Flight / Next.js RCE Advisory Fix
### Summary
Updated the laza Next.js project to address the React Flight / Next.js RCE advisory by upgrading Next.js to a patched version.
### Vulnerability Assessment
The project is affected by the advisory because it:
- ✅ Uses Next.js 15.3.4 (vulnerable minor version)
- ❌ Does NOT use React Flight packages (react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack)
Since the project uses Next.js, only the Next.js upgrade was needed per the advisory instructions.
### Changes Made
#### Modified Files
- `package.json`: Upgraded Next.js from 15.3.4 to 15.3.6 (patched version for 15.3.x)
- `package-lock.json`: Updated lockfile to reflect Next.js 15.3.6 (npm run)
#### Notes on React and React-DOM
Per the advisory guidance, React and React-DOM were NOT manually upgraded. The patched Next.js 15.3.6 version automatically supplies the correct patched React dependency versions, so they were left at their existing versions (19.1.1).
### Implementation Details
1. **Affected Package Detection**: Identified that the project uses Next.js 15.3.4 and does not use any React Flight packages.
2. **Package Upgrade**: Applied the upgrade rule for Next.js 15.3.x:
- Next.js: 15.3.4 → 15.3.6 (patched version)
- React: 19.1.1 (no change - Next.js provides compatibility)
- React-DOM: 19.1.1 (no change - Next.js provides compatibility)
3. **Dependency Installation**: Ran `npm install` to update the lockfile with the patched versions. The installation succeeded without errors (with expected pre-existing npm audit warnings unrelated to this change).
4. **Build Verification**:
- Ran `npm run build` to verify the patched Next.js version builds correctly
- The compilation succeeded ("✓ Compiled successfully in 16.0s")
- The build error is unrelated to the vulnerability fix (missing Google Maps API key in application code)
5. **Linter Check**: Ran `npm run lint` to ensure no new linting errors were introduced by the version update. Pre-existing linting issues remain but are not caused by this change.
### Verification
- ✅ Next.js version in package.json: 15.3.6
- ✅ Next.js version in package-lock.json: 15.3.6
- ✅ Next.js compilation: Successful with patched version
- ✅ No breaking changes introduced
- ✅ No unintended file modifications
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 laza. 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