react-server-dom-webpack, react-server-dom-turbopack: Meta React Server Components Remote Code Execution Vulnerability
There is evidence it is being used against people now, on something Phylax follows.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- react-server-dom-webpack (npm): from 19.0.0, before 19.0.1
- react-server-dom-webpack (npm): from 19.1.0, before 19.1.2
- react-server-dom-webpack (npm): from 19.2.0, before 19.2.1
- react-server-dom-turbopack (npm): from 19.0.0, before 19.0.1
- react-server-dom-turbopack (npm): from 19.1.0, before 19.1.2
- react-server-dom-turbopack (npm): from 19.2.0, before 19.2.1
- react-server-dom-parcel (npm): from 19.0.0, before 19.0.1
- react-server-dom-parcel (npm): from 19.1.0, before 19.1.2
- react-server-dom-parcel (npm): from 19.2.0, before 19.2.1
The fix
react-server-dom-webpack (npm) fixed in 19.0.1
npmnpm install react-server-dom-webpack@19.0.1pnpmpnpm add react-server-dom-webpack@19.0.1yarnyarn add react-server-dom-webpack@19.0.1bunbun add react-server-dom-webpack@19.0.1Check what is installednpm ls react-server-dom-webpackPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-webpack to 19.0.1 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.react-server-dom-webpack (npm) fixed in 19.1.2
npmnpm install react-server-dom-webpack@19.1.2pnpmpnpm add react-server-dom-webpack@19.1.2yarnyarn add react-server-dom-webpack@19.1.2bunbun add react-server-dom-webpack@19.1.2Check what is installednpm ls react-server-dom-webpackPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-webpack to 19.1.2 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.react-server-dom-webpack (npm) fixed in 19.2.1
npmnpm install react-server-dom-webpack@19.2.1pnpmpnpm add react-server-dom-webpack@19.2.1yarnyarn add react-server-dom-webpack@19.2.1bunbun add react-server-dom-webpack@19.2.1Check what is installednpm ls react-server-dom-webpackPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-webpack to 19.2.1 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.react-server-dom-turbopack (npm) fixed in 19.0.1
npmnpm install react-server-dom-turbopack@19.0.1pnpmpnpm add react-server-dom-turbopack@19.0.1yarnyarn add react-server-dom-turbopack@19.0.1bunbun add react-server-dom-turbopack@19.0.1Check what is installednpm ls react-server-dom-turbopackPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-turbopack to 19.0.1 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.react-server-dom-turbopack (npm) fixed in 19.1.2
npmnpm install react-server-dom-turbopack@19.1.2pnpmpnpm add react-server-dom-turbopack@19.1.2yarnyarn add react-server-dom-turbopack@19.1.2bunbun add react-server-dom-turbopack@19.1.2Check what is installednpm ls react-server-dom-turbopackPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-turbopack to 19.1.2 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.react-server-dom-turbopack (npm) fixed in 19.2.1
npmnpm install react-server-dom-turbopack@19.2.1pnpmpnpm add react-server-dom-turbopack@19.2.1yarnyarn add react-server-dom-turbopack@19.2.1bunbun add react-server-dom-turbopack@19.2.1Check what is installednpm ls react-server-dom-turbopackPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-turbopack to 19.2.1 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.react-server-dom-parcel (npm) fixed in 19.0.1
npmnpm install react-server-dom-parcel@19.0.1pnpmpnpm add react-server-dom-parcel@19.0.1yarnyarn add react-server-dom-parcel@19.0.1bunbun add react-server-dom-parcel@19.0.1Check what is installednpm ls react-server-dom-parcelPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-parcel to 19.0.1 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.react-server-dom-parcel (npm) fixed in 19.1.2
npmnpm install react-server-dom-parcel@19.1.2pnpmpnpm add react-server-dom-parcel@19.1.2yarnyarn add react-server-dom-parcel@19.1.2bunbun add react-server-dom-parcel@19.1.2Check what is installednpm ls react-server-dom-parcelPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-parcel to 19.1.2 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.react-server-dom-parcel (npm) fixed in 19.2.1
npmnpm install react-server-dom-parcel@19.2.1pnpmpnpm add react-server-dom-parcel@19.2.1yarnyarn add react-server-dom-parcel@19.2.1bunbun add react-server-dom-parcel@19.2.1Check what is installednpm ls react-server-dom-parcelPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency react-server-dom-parcel to 19.2.1 or the nearest later release, to fix CVE-2025-55182. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploited · Confirmed
It is in CISA's Known Exploited Vulnerabilities catalogue.
Exploited · Confirmed
CISA's assessment in the CVE record says exploitation is active.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Exploitable · Confirmed
EPSS puts the chance of exploitation in the next 30 days at over 99%.
FIRST EPSSStated
Timeline
- First published here, as "Listed".
- Level changed from "Listed" to "Act now".
- Fixed releases changed: added react-server-dom-webpack 19.0.1, react-server-dom-webpack 19.1.2, react-server-dom-webpack 19.2.1, react-server-dom-turbopack 19.0.1, react-server-dom-turbopack 19.1.2, react-server-dom-turbopack 19.2.1, react-server-dom-parcel 19.0.1, react-server-dom-parcel 19.1.2, react-server-dom-parcel 19.2.1.
- Evidence added: CISA's assessment in the CVE record says exploitation is active. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))
- Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)