Skip to content
JournalTORIS / FIELD NOTES

← Blog Learning notes

[React] Critical Security Vulnerability in React Server Components (CVE-2025-55182)

Analysis and response guide for CVE-2025-55182 (CVSS 10.0), an unauthenticated RCE in React Server Components: affected versions, patches for Next.js and React, and a stack checklist.

6 min read Read the Korean original

Joohwan Yu · Founder, Full Stack Developer

Toris · Published

Contents

🚨 Critical Security Vulnerability Found in React Server Components

Q. What is the React Server Components vulnerability CVE-2025-55182, and how do I respond? It is an unauthenticated remote code execution (RCE) vulnerability (CVSS 10.0) in RSC payload deserialization, and you should update to a patched version immediately.

As the head of a studio that runs several products directly, whenever a security notice like this appears, I always judge in the same order. First I determine “is our stack within range of this vulnerability?” If it is, I decide “which service do I touch first?” and then “how do we roll it out without downtime?” Toris runs several Next.js-based products, including MemeCatch (밈캐치), so an RSC vulnerability is not someone else’s problem. Checking our stack is the same as keeping the service trust we promised our users. Below is a record that covers both the technical details of this CVE and what I decided first from an operations owner’s perspective.

On December 3, 2025, the React team disclosed an unauthenticated remote code execution (RCE) vulnerability in React Server Components. The vulnerability was assigned CVE-2025-55182 and rated CVSS 10.0 (the highest severity).

Vulnerability overview

This vulnerability occurs during payload deserialization in React Server Functions. When an attacker sends a malicious HTTP request to a Server Function endpoint, remote code execution on the server becomes possible during React’s deserialization of it.

⚠️ Important: Even an app that doesn’t implement any React Server Function endpoints can be vulnerable if it supports React Server Components.

Affected versions

The vulnerability was found in specific versions of the following packages:

  • react-server-dom-webpack
  • react-server-dom-parcel
  • react-server-dom-turbopack

Vulnerable versions:

  • 19.0.0
  • 19.1.0
  • 19.1.1
  • 19.2.0

Fixed versions:

  • 19.0.1
  • 19.1.2
  • 19.2.1

Affected frameworks and bundlers

The following React frameworks and bundlers depend on or include the vulnerable React packages:

  • Next.js
  • React Router
  • Waku
  • @parcel/rsc
  • @vitejs/plugin-rsc
  • rwsdk (Redwood SDK)

Immediate action required

This vulnerability requires an immediate update. Hosting providers have applied temporary mitigations, but don’t rely on them: you must update to the latest patched version.

As an operations owner, I set patch priority as “degree of external exposure × user impact.” For an unauthenticated RCE at CVSS 10.0, this calculation is simple. Products that receive public traffic go up first, and internal or low-traffic ones are pushed back. I treat a mitigation only as a way to buy time, not as the end of the situation.

📦 How to update

Next.js

Rather than jumping to a major upgrade, I prefer to move to the latest patch of the current release line. Keeping the change scope minimal makes it easier to deploy without downtime and speeds up rollback decisions. For the actual rollout, I keep this order: verify the build and RSC behavior on staging, move to a zero-downtime deploy, and then check again that the version has actually changed in production.

If you use Next.js, update to the latest patch version of the release line you are currently on:

# Next.js 15.0.x
npm install next@15.0.5

# Next.js 15.1.x
npm install next@15.1.9

# Next.js 15.2.x
npm install next@15.2.6

# Next.js 15.3.x
npm install next@15.3.6

# Next.js 15.4.x
npm install next@15.4.8

# Next.js 15.5.x
npm install next@15.5.7

# Next.js 16.0.x (currently recommended)
npm install next@16.0.7

If you are using a canary version of Next.js 14.3.0-canary.77 or later, downgrade to the latest stable 14.x:

npm install next@14

React and React DOM

Update React and React DOM to the latest version:

npm install react@19.2.1 react-dom@19.2.1

Or if you use pnpm:

pnpm update react@19.2.1 react-dom@19.2.1

React Server Components packages

If your project uses them directly, update the following packages too:

# react-server-dom-webpack
npm install react-server-dom-webpack@latest

# react-server-dom-parcel
npm install react-server-dom-parcel@latest

# react-server-dom-turbopack
npm install react-server-dom-turbopack@latest

Other frameworks

React Router

If you use React Router’s unstable RSC API:

npm install react@latest react-dom@latest
npm install react-server-dom-parcel@latest
npm install react-server-dom-webpack@latest
npm install @vitejs/plugin-rsc@latest

Waku

npm install react@latest react-dom@latest react-server-dom-webpack@latest waku@latest

@vitejs/plugin-rsc

npm install react@latest react-dom@latest @vitejs/plugin-rsc@latest

Advertisement

🔍 When the vulnerability does not apply

You are not affected by this vulnerability if any of the following conditions apply:

  1. A React app that doesn’t use a server: when you use only the client side
  2. Using a framework/bundler that doesn’t support React Server Components: when you don’t use React Server Components features

📅 Timeline

  • November 29, 2025: Lachlan Davidson reported the security vulnerability through the Meta Bug Bounty
  • November 30, 2025: Meta security researchers confirmed it and began fix work with the React team
  • December 1, 2025: The fix was created, and it was verified and mitigations implemented in cooperation with hosting providers and open-source projects
  • December 3, 2025: The fix was published to npm and the vulnerability was publicly disclosed as CVE-2025-55182

💡 Security best practices

To prevent vulnerabilities like this, follow these points:

  1. Regular dependency updates: Update immediately when a security patch is announced
  2. Subscribe to security alerts: Subscribe to security alerts for the frameworks you use, such as React and Next.js
  3. Dependency vulnerability scanning: Run npm audit or pnpm audit regularly
  4. Principle of least privilege: Implement proper authentication and authorization checks in Server Functions

📚 References

🎯 Conclusion

A critical security vulnerability was found in React Server Components. Update to the latest patched version immediately to protect your application from the security threat. In production especially, it is important to apply the update as soon as possible.

Toris’s security response principles

The procedure Toris follows when we encounter a notice like this is simple. We subscribe to official security notices; when one appears, we first determine whether our stack is in the affected range; if it is, we patch in order of exposure and then re-verify the version actually in effect after redeploying. The checklist below carries this procedure over to the per-service level as is, so just follow it in order.

If you need maintenance or operations that include this kind of security response, please contact Toris.

Our stack checklist

Toris runs its blog on Next.js and some services on Astro. Check the procedure below in order to determine whether you are affected by this vulnerability and to respond.

  • Check installed versions: Run npm list next react react-dom react-server-dom-webpack (pnpm list ... for pnpm) to check whether a vulnerable version (React 19.0.0 / 19.1.0 / 19.1.1 / 19.2.0) is installed.
  • Determine RSC usage: Check whether you use Server Components or Server Functions in the Next.js App Router. If it is a purely client-side app or doesn’t use RSC, you are not affected by this vulnerability.
  • Check Astro projects: Astro doesn’t use React Server Components by default, and if you use React only as islands via @astrojs/react, there is no RSC deserialization path, so you are outside the affected range. If you attached a separate RSC integration, apply the same version check above.
  • Apply the patch: Update to the latest patch of the release line you use. For example: npm install next@16.0.7, npm install react@19.2.1 react-dom@19.2.1. The fixed versions are 19.0.1 / 19.1.2 / 19.2.1.
  • Verify the build: Confirm the build succeeds with npm run build (or pnpm build), and check that RSC features work properly.
  • Redeploy and confirm: After redeploying to production, check again the version actually in effect with npm list react react-dom. Don’t rely only on the hosting provider’s temporary mitigation.
  • Scan for remaining vulnerabilities and subscribe to alerts: Check with npm audit (or pnpm audit) that no vulnerable dependencies remain, and subscribe to the React official blog and Next.js/Vercel security notices to track follow-up patches.

Updated: December 3, 2025
Author: Toris
Category: React, Security

Advertisement