Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilityopen-source-dependency-vulnerabilitywidely-deployed-product-advisorydetection-content-update

High-severity DoS in React Server Components (CVE-2026-23864) with incomplete prior fixes

Vulnerability Disclosure · 3 sources · Updated 5mo ago · First seen Jan 27, 2026

High-severity DoS in React Server Components (CVE-2026-23864) with incomplete prior fixes

React maintainers disclosed that earlier mitigations for denial-of-service issues in React Server Components were incomplete, leaving multiple DoS conditions still exploitable as CVE-2026-23864 (CVSS 7.5). The issue affects the react-server-dom-* packages used by bundlers—react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack—across versions 19.0.0–19.2.3. An attacker can send specially crafted HTTP requests to Server Function endpoints to drive resource exhaustion, potentially causing server crashes, out-of-memory conditions, or excessive CPU usage; applications that do not use a server-side React Server Components/Server Functions setup (e.g., purely client-side SPAs) are not impacted.

Vercel reported the vulnerabilities were responsibly disclosed and emphasized they do not enable RCE, but can still materially impact availability for affected deployments, including those using Next.js and other frameworks/bundlers that embed React Server Components. Vercel deployed new WAF rules to provide automatic mitigation for projects hosted on its platform, while warning that WAF protections are not a substitute for patching. Recommended remediation is to upgrade to patched releases: React 19.0.4, 19.1.5, 19.2.4, and updated downstream framework versions (including multiple Next.js fixed releases) as provided by maintainers.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Jan 26, 2026
  1. Jan 26, 202610mo ago

    Vercel deploys WAF mitigations for all hosted projects

    Vercel created and deployed new mitigation rules to the Vercel WAF to automatically protect all Vercel-hosted projects at no additional cost. The company emphasized that WAF protection alone was not sufficient and that customers should still upgrade to patched React and framework releases.

  2. Jan 26, 202610mo ago

    Next.js publishes fixes across supported branches

    Downstream framework fixes were released for Next.js across multiple supported branches and canary versions to address the React Server Components denial-of-service issue. Users were advised to update framework versions in addition to relying on upstream React patches.

  3. Jan 26, 202610mo ago

    React issues advisory for CVE-2026-23864 and releases patched versions

    React disclosed CVE-2026-23864, warning that earlier fixes were incomplete and that affected server-dom packages remained vulnerable across versions 19.0.0 through 19.2.3. The project released patched versions 19.0.4, 19.1.5, and 19.2.4 and urged developers to upgrade immediately.

  4. Jan 26, 202610mo ago

    Researchers responsibly disclose React Server Components DoS flaws

    Multiple researchers from Winfunc Research, GMO Flatt Security, and Tencent Security YUNDING LAB responsibly disclosed high-severity denial-of-service vulnerabilities affecting React Server Components and Server Function endpoints. The flaws could be triggered with specially crafted HTTP requests to cause crashes, out-of-memory conditions, or excessive CPU usage, but were explicitly stated not to enable remote code execution.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
React
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.