CVE-2025-55182: which React Server Components versions to upgrade
Short answer
CVE-2025-55182 is unauthenticated remote code execution in React Server Components, rated CVSS 10.0. It affects react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack at 19.0.0, 19.1.0, 19.1.1, and 19.2.0. Patched revisions are 19.0.1, 19.1.2, and 19.2.1. Next.js apps that vendor those packages need the patched Next.js release for their line; follow the React security post because later fixes moved the minimum. Apps with no server, and apps that do not use a bundler that supports React Server Components, are not affected. Check with npm ls. Do not send an exploit payload.
Last updated · Sekrd Research
- CVE-2025-55182, disclosed December 3, 2025. CVSS 10.0. Unauthenticated RCE in the RSC Flight protocol.
- Affected packages: react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack at 19.0.0, 19.1.0, 19.1.1, and 19.2.0.
- Patched package versions: 19.0.1, 19.1.2, and 19.2.1.
- Frameworks that embed those packages include Next.js, React Router, Waku, Parcel RSC, and the Vite RSC plugin. Next.js tracked the same issue as CVE-2025-66478, later recorded as a duplicate.
Who is affected
The React advisory is narrower than “you use React.” If the app does not run a server, it is not affected. If nothing in the stack supports React Server Components, it is not affected. A Vite SPA from Bolt with no RSC plugin is outside this CVE. A Next.js app from v0 or Cursor that uses the App Router and Server Actions is inside it, because Next.js depends on the vulnerable packages.
The bug is in how React decodes a payload sent to a Server Function endpoint. The React team’s write-up says an app can still be vulnerable if it supports Server Components even when you did not write a Server Function yourself. That is why “we don’t use server actions” is not a reason to skip the upgrade.
How to check
- Ask the lockfile. Do not infer the version from the website’s HTML. Sekrd does not do that either, for the same reason: the homepage is not a version oracle.
npm ls react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack next
A pin at 19.0.0, 19.1.0, 19.1.1, or 19.2.0 of those three packages is the vulnerable set named in GHSA-fv66-9v8q-g76r. 19.0.1, 19.1.2, and 19.2.1 are the first patched revisions in each line. Anything newer than the patched revision in that line is what you want; do not downgrade from a later patched release to the first patched release.
- Upgrade the framework, not only the transitive package. Next.js vendors these. The React security blog lists
npm install next@…per release line and has been updated as follow-up issues landed. Use that post, or the current Next.js advisory, the day you patch. Copying a version number out of a secondary blog will go stale. CVE-2025-66478 is the Next.js CVE id that was then treated as a duplicate of CVE-2025-55182; patching Next.js is still required. - Redeploy. A lockfile change does nothing until the server running the old bundle is replaced. Serverless platforms pick this up on the next deploy. A long-lived Node process keeps the old code until you restart it.
- Do not send a proof-of-concept payload to your production server, and do not leave one in the repo “as a test.” Public exploits exist. Your check is the version. A WAF rule is a temporary layer the React post mentions; it is not a patch.
What a scan can honestly say
On a free scan, Sekrd reports this only when the shipped JavaScript pins one of those three packages at one of the four vulnerable versions. A blog post that mentions the numbers, including this one, does not match. The patched revisions do not match. The finding says the pin is present and that you should confirm the running server; it does not send a Flight payload. If the vulnerable code is only on the server and never referenced in the client bundle, the lockfile check above is the one that sees it. Run both.
Start with a free scan of the live URL. The version command takes a minute in the repo. Related launch checks for generated Next.js apps are in how to secure a v0 app. On October 14, 2026 React published a wider Server Components advisory, GHSA-xqc2-xf4c-x3h3. The four versions above are not the whole of that later range. Read the October 14 notes before you treat a post-19.0.1 pin as finished.
Frequently asked questions
What is CVE-2025-55182?
A CVSS 10.0 unauthenticated remote code execution vulnerability in React Server Components, disclosed December 3, 2025. It affects react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0. Patched versions are 19.0.1, 19.1.2, and 19.2.1.
Is a Next.js app affected by CVE-2025-55182?
Next.js apps that include the vulnerable React Server Components packages are affected, including apps that did not intentionally add a Server Function. Upgrade Next.js to the patched release for your line listed in the React security blog. CVE-2025-66478 was recorded as a duplicate of CVE-2025-55182.
How do I check CVE-2025-55182 without an exploit?
Run npm ls on react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack, and next. If you see 19.0.0, 19.1.0, 19.1.1, or 19.2.0 of those packages, upgrade to 19.0.1, 19.1.2, or 19.2.1 or later in that line and redeploy. Do not send an exploit payload.
Sources
Don't ship until you're sekrd
Run a free scan to find the vulnerabilities your AI missed.
Scan Your App Free