-
Notifications
You must be signed in to change notification settings - Fork 4
docs: add changelog entry for React/Next.js security update (CVE-2025-66478) #2515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| ## Security update: React Server Components vulnerability patched | ||
|
|
||
| We've updated our platform to address a critical security vulnerability (CVE-2025-66478) in React Server Components. This vulnerability, rated CVSS 10.0, could allow remote code execution when processing attacker-controlled requests in unpatched environments. | ||
|
|
||
| The vulnerability originates in the upstream React implementation (CVE-2025-55182) and affects Next.js applications using the App Router with React Server Components. | ||
|
|
||
| ### What we did | ||
|
|
||
| We upgraded our platform dependencies to the patched versions: | ||
|
|
||
| - **Next.js**: Updated from 15.5.4 to 15.5.7 | ||
| - **React**: Updated from 19.0.0 to 19.0.1 | ||
| - **React-DOM**: Updated from 19.0.0 to 19.0.1 | ||
|
|
||
| These versions include the hardened React Server Components implementation that resolves the vulnerability. | ||
|
|
||
| ### Impact on Fern users | ||
|
|
||
| No action is required from Fern Docs users. The security patch has been applied to all Fern-hosted documentation sites automatically. | ||
|
|
||
| For self-hosted deployments, we recommend updating to the latest Fern platform version to ensure you have the security fix. | ||
|
|
||
| ### References | ||
|
|
||
| - [Next.js Security Advisory: CVE-2025-66478](https://nextjs.org/blog/CVE-2025-66478) | ||
| - [Next.js 15.5.7 Release](https://github.com/vercel/next.js/releases/tag/v15.5.7) | ||
| - [React 19.0.1 Release](https://github.com/facebook/react/releases/tag/v19.0.1) | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chdeskur imo we dont need to be this explicit in the exact versions we are using