Skip to content

Commit 04a4959

Browse files
committed
add update instructions
1 parent 4704ce6 commit 04a4959

File tree

1 file changed

+83
-2
lines changed

1 file changed

+83
-2
lines changed

src/content/blog/2025/12/03/critical-security-vulnerability-in-react-server-components.md

Lines changed: 83 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,13 +50,94 @@ We will update this post with upgrade instructions on how to upgrade as they bec
5050

5151
An unauthenticated attacker could craft a malicious HTTP request to any Server Function endpoint that, when deserialized by React, achieves remote code execution on the server. Further details of the vulnerability will be provided after the rollout of the fix is complete.
5252

53-
### Timeline {/*timeline*/}
53+
## Update Instructions {/*update-instructions*/}
54+
55+
### Next.js {/*update-next-js*/}
56+
57+
All users should upgrade to the latest patched version in their release line:
58+
59+
```bash
60+
npm install [email protected] // for 15.0.x
61+
npm install [email protected] // for 15.1.x
62+
npm install [email protected] // for 15.2.x
63+
npm install [email protected] // for 15.3.x
64+
npm install [email protected] // for 15.4.x
65+
npm install [email protected] // for 15.5.x
66+
npm install [email protected] // for 16.0.x
67+
```
68+
69+
If you are on Next.js 14.3.0-canary.77 or a later canary release, downgrade to the latest stable 14.x release:
70+
71+
```bash
72+
npm install next@14
73+
```
74+
75+
See the [Next.js changelog](https://vercel.com/changelog/cve-2025-55182) for more info.
76+
77+
### React Router {/*update-react-router*/}
78+
79+
If you are using React Router's unstable RSC APIs, you should upgrade the following package.json dependencies if they exist:
80+
81+
```bash
82+
npm install react@latest
83+
npm install react-dom@latest
84+
npm install react-server-dom-parcel@latest
85+
npm install react-server-dom-webpack@latest
86+
```
87+
88+
### Redwood SDK {/*update-redwood-sdk*/}
89+
90+
Upgrade to the latest `react-server-dom-webpack`:
91+
92+
```bash
93+
npm install react@latest react-dom@latest react-server-dom-webpack@latest
94+
```
95+
96+
See [Redwood docs](https://docs.rwsdk.com/migrating/) for more migration instructions.
97+
98+
### Waku {/*update-waku*/}
99+
100+
Upgrade to the latest `react-server-dom-webpack`:
101+
102+
```bash
103+
npm install react@latest react-dom@latest react-server-dom-webpack@latest
104+
```
105+
106+
### `vite/plugin-rsc` {/*vite-plugin-rsc*/}
107+
108+
A patch has not been published yet, we will update this post when the patch is available.
109+
110+
### `react-server-dom-parcel` {/*update-react-server-dom-parcel*/}
111+
112+
Update to the latest version:
113+
114+
```bash
115+
npm install react@latest react-dom@latest react-server-dom-parcel@latest
116+
```
117+
118+
### `react-server-dom-turbopack` {/*update-react-server-dom-turbopack*/}
119+
120+
Update to the latest version:
121+
122+
```bash
123+
npm install react@latest react-dom@latest react-server-dom-turbopack@latest
124+
```
125+
126+
### `react-server-dom-webpack` {/*update-react-server-dom-webpack*/}
127+
128+
Update to the latest version:
129+
130+
```bash
131+
npm install react@latest react-dom@latest react-server-dom-webpack@latest
132+
```
133+
134+
## Timeline {/*timeline*/}
54135

55136
* **November 29th**: Lachlan Davidson reported the security vulnerability via [Meta Bug Bounty](https://bugbounty.meta.com/).
56137
* **November 30th**: Meta security researchers confirmed and began working with the React team on a fix.
57138
* **December 1st**: A fix was created and the React team began working with affected hosting providers and open source projects to validate the fix, implement mitigations and roll out the fix
58139
* **December 3rd**: The fix was published to npm and the publicly disclosed as CVE-2025-55182.
59140

60-
### Attribution {/*attribution*/}
141+
## Attribution {/*attribution*/}
61142

62143
Thank you to [Lachlan Davidson](https://github.com/lachlan2k) for discovering, reporting, and working to help fix this vulnerability.

0 commit comments

Comments
 (0)