You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/blog/2025/12/03/critical-security-vulnerability-in-react-server-components.md
+12-36Lines changed: 12 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,15 +20,9 @@ React Server Components に、認証不要のリモートコード実行の脆
20
20
21
21
---
22
22
23
-
<<<<<<< HEAD
24
23
11 月 29 日、Lachlan Davidson 氏が React のセキュリティ脆弱性を報告しました。これは、React Server Function のエンドポイントに送信されたペイロードを React がデコードする際の欠陥を悪用することで、未認証状態でのリモートコード実行を可能にするものです。
25
24
26
25
アプリが React のサーバ関数 (Server Function) のエンドポイントを実装していない場合でも、React Server Components をサポートしている場合は脆弱性の影響を受ける可能性があります。
27
-
=======
28
-
On November 29th, Lachlan Davidson reported a security vulnerability in React that allows unauthenticated remote code execution by exploiting a flaw in how React decodes payloads sent to React Server Function endpoints.
29
-
30
-
Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
Some React frameworks and bundlers depended on, had peer dependencies for, or included the vulnerable React packages. The following React frameworks & bundlers are affected: [next](https://www.npmjs.com/package/next), [react-router](https://www.npmjs.com/package/react-router), [waku](https://www.npmjs.com/package/waku), [@parcel/rsc](https://www.npmjs.com/package/@parcel/rsc), [@vitejs/plugin-rsc](https://www.npmjs.com/package/@vitejs/plugin-rsc), and [rwsdk](https://www.npmjs.com/package/rwsdk).
55
-
56
-
See the [update instructions below](#update-instructions) for how to upgrade to these patches.
See the [Next.js blog](https://nextjs.org/blog/security-update-2025-12-11) for the latest update instructions and the [previous changelog](https://nextjs.org/blog/CVE-2025-66478) for more info.
For React Native users not using a monorepo or `react-dom`, your `react`version should be pinned in your `package.json`, and there are no additional steps needed.
This is required to mitigate the security advisory, but you do not need to update `react`and`react-dom`so this will not cause the version mismatch error in React Native.
<BlogCardtitle="React Server Components における重大なセキュリティ脆弱性"date="December 3, 2025"url="/blog/2025/12/03/critical-security-vulnerability-in-react-server-components">
21
-
=======
22
19
<BlogCardtitle="Denial of Service and Source Code Exposure in React Server Components"date="December 11, 2025"url="/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components">
23
20
24
-
Security researchers have found and disclosed two additional vulnerabilities in React Server Components while attempting to exploit the patches in last week’s critical vulnerability...
21
+
Security researchers have found and disclosed two additional vulnerabilities in React Server Components while attempting to exploit the patches in last week's critical vulnerability...
25
22
26
23
</BlogCard>
27
24
28
-
<BlogCardtitle="Critical Security Vulnerability in React Server Components"date="December 3, 2025"url="/blog/2025/12/03/critical-security-vulnerability-in-react-server-components">
29
-
>>>>>>> 2da4f7fbd90ddc09835c9f85d61fd5644a271abc
25
+
<BlogCardtitle="React Server Components における重大なセキュリティ脆弱性"date="December 3, 2025"url="/blog/2025/12/03/critical-security-vulnerability-in-react-server-components">
30
26
31
27
React Server Components に、認証不要のリモートコード実行の脆弱性が存在します。バージョン 19.0.1、19.1.2、19.2.1 で修正が公開されました。直ちにアップグレードすることを推奨します。
0 commit comments