Skip to main content
Mallory
HighVulnerability

CVE-2026-23870: Denial of Service in React Server Components Form-Data Decoding

Published May 6, 2026 · Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Meta Platforms
IdentifiersCVE-2026-23870CWE-400 · Uncontrolled Resource Consumption

CVE-2026-23870 is a denial-of-service vulnerability in React Server Components server-function request decoding. It affects react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack versions 19.0.0–19.0.5, 19.1.0–19.1.6, and 19.2.0–19.2.5. When reconstructing nested FormData objects, the vulnerable decoder scans all submitted fields separately for each $K reference. Because attackers control both counts, decoding work grows with their product. These synchronous scans can block the Node.js event loop before application Server Action logic executes, causing excessive CPU consumption and service unavailability. Vulnerable integrations include Next.js applications exposing Server Functions.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote attackers can exhaust server resources, interrupt legitimate request processing, and cause timeouts, out-of-memory exceptions, or server crashes. Repeated requests can sustain downtime and cause load balancers to remove affected instances from service, producing HTTP 503 responses. A demonstrated request of approximately 900 KB induced roughly 100 million comparisons and several seconds of unresponsiveness. The established impact is on availability; confidentiality compromise, integrity compromise, and code execution are not established.

Mitigation

If you can’t patch tonight, do this now.

No complete workaround is established. Until patched, restrict access to vulnerable Server Function endpoints using controls that run before React request decoding. Apply reverse-proxy or edge request-rate limits and body-size limits as supplementary safeguards; relatively small requests can still generate disproportionate processing work. Applicable managed WAF protections may reduce exposure but must not replace patching. Monitor multipart POST activity, CPU saturation, request queues, and health-check failures. Authentication or validation implemented inside a Server Action executes too late to prevent the expensive decoding.

Remediation

Patch, then assume compromise.

Upgrade the affected React Server Components packages to 19.0.6, 19.1.7, or 19.2.6 for the corresponding release branch, or a later fixed release. Inspect resolved dependencies, including framework-managed or bundled copies, rather than relying solely on top-level React versions. Next.js fixes for this vulnerability were released in 15.5.16 and 16.2.5; prefer the latest supported security release because subsequent updates address additional vulnerabilities. Rebuild and redeploy all affected application artifacts. The React fix replaces repeated full-field scans with shared, single-pass processing.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Meta PlatformsReact-Server-Dom-Parcelapplication
Meta PlatformsReact-Server-Dom-Turbopackapplication
Meta PlatformsReact-Server-Dom-Webpackapplication
FAQ

Frequently asked questions

Is CVE-2026-23870 exploited in the wild?
As of Oct 21, 2026, Mallory has no reports of CVE-2026-23870 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-23870?
As of Oct 21, 2026, Mallory has not confirmed a public exploit for CVE-2026-23870. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2026-23870?
Upgrade the affected React Server Components packages to 19.0.6, 19.1.7, or 19.2.6 for the corresponding release branch, or a later fixed release. Inspect resolved dependencies, including framework-managed or bundled copies, rather than relying solely on top-level React versions.
What products are affected by CVE-2026-23870?
Meta Platforms React-Server-Dom-Parcel, Meta Platforms React-Server-Dom-Turbopack, and Meta Platforms React-Server-Dom-Webpack.
How severe is CVE-2026-23870?
CVE-2026-23870 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.5% (75th percentile) as of Oct 21, 2026.
Activity feed

Recent activity

30 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cryptika blogNews · Oct 9, 2026React Server Components Flaw Lets Attackers Freeze Next.js Servers With a Single POST Request | Cryptika CybersecurityA CVSS 7.5 resource-exhaustion vulnerability in React Server Components form-data parsing. Each attacker-controlled $K reference triggers a full scan of submitted fields, creating excessive repeated processing before Server Action logic executes. A roughly 900 KB proof-of-concept request can cause approximately 100 million string comparisons, potentially blocking the Node.js event loop. React's advisory also describes excessive CPU usage, out-of-memory conditions, and server crashes. Affected release ranges are 19.0.0–19.0.5, 19.1.0–19.1.6, and 19.2.0–19.2.5; fixes are available in 19.0.6, 19.1.7, and 19.2.6. Recommended mitigations include reverse-proxy POST body-size limits, request-rate controls, and timeouts, but patching remains the primary fix.Read more ↗reddit netsecNews · Oct 8, 2026A Single POST Freezes Any Next.js Server : r/netsecA denial-of-service vulnerability in React form processing, described as affecting Next.js servers. Unbounded scanning of request fields for each contained reference allows a single approximately 900 KB POST request to trigger 100 million checks and freeze the server. The post reports that the vulnerability was fixed, but provides no patched versions.Read more ↗simon koeck blogNews · Oct 8, 2026CVE-2026-23870: A Single POST Freezes Any Next.js Server | Simon KoeckA denial-of-service vulnerability in React Server Components server-action form decoding. Each attacker-controlled $K nested-form pointer triggers a synchronous scan of all submitted fields, producing quadratic processing overhead that blocks the Node.js event loop. Existing nesting and argument limits do not prevent exploitation. An attacker needs a reachable server action and its discoverable action ID; public actions require no authentication. The researcher demonstrated approximately four seconds of server unresponsiveness from one roughly 900 KB request, with repeated requests causing prolonged outages and load-balancer 503 errors. React 19.0, 19.1, and 19.2 releases before 19.0.6, 19.1.7, and 19.2.6, respectively, are affected. The patch replaces repeated scans with a shared single pass through the request fields.Read more ↗cyber security newsNews · May 8, 2026Multiple Critical Vulnerabilities Patched in Next.js and React Server ComponentsA high-severity denial-of-service vulnerability in React Server Components / Next.js App Router caused by unsafe deserialization in the React Flight protocol, allowing crafted requests to trigger excessive CPU usage.Read more ↗
+3 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity22Community discussion across Reddit, Mastodon, and other social sources.