Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-23869: React Server Components Server Function Deserialization Denial of Service

Published Apr 8, 2026 · Updated 25 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.6%76th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-23869CWE-400 · Uncontrolled Resource Consumption

CVE-2026-23869 is a denial-of-service vulnerability in the Server Function request deserialization logic of React Server Components. It affects react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack versions 19.0.0–19.0.4, 19.1.0–19.1.5, and 19.2.0–19.2.4. An unauthenticated remote attacker can submit a specially crafted HTTP request that causes excessive CPU consumption for approximately 60 seconds before processing terminates with a catchable error. The vulnerability follows an incomplete remediation of CVE-2026-23864. Affected downstream deployments include Next.js applications using the App Router.

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.

Exploitation can degrade application responsiveness or deny service to legitimate users through prolonged backend CPU consumption. Repeated malicious requests can compound resource exhaustion and sustain service disruption. The vulnerability affects availability; no confidentiality or integrity impact is identified. The request ultimately produces a catchable error rather than necessarily crashing the server.

Mitigation

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

If immediate patching is not possible, prevent untrusted access to vulnerable Server Function endpoints. Vercel deployed platform WAF rules to protect hosted projects, but these protections are not a substitute for upgrading affected dependencies.

Remediation

Patch, then assume compromise.

Upgrade all affected React Server Components packages to versions containing the CVE-2026-23869 fix: 19.0.5, 19.1.6, or 19.2.5, according to the release branch. For affected Next.js App Router applications, upgrade 13.x, 14.x, and vulnerable 15.x installations to 15.5.15 or later, and vulnerable 16.x installations to 16.2.3 or later. Audit resolved dependencies, including transitive framework dependencies. Because the initial React fix versions are affected by the separate CVE-2026-23870, prefer 19.0.6, 19.1.7, or 19.2.6 or later appropriately patched releases.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-23869-ExploitThis repository is a real exploit/PoC set for CVE-2026-23869 ('React2DoS'), an unauthenticated remote denial-of-service issue in React Server Components Flight protocol deserialization. The repo contains four files: a Nuclei template (CVE-2026-23869.yaml), a Python PoC (poc.py), a Bash helper for extracting Next.js Server Action IDs (extract-action-ids.sh), and a README. Because the repository includes a Nuclei template, it appears framework-associated; the template is the main exploit/detection artifact, while the Python and Bash files provide standalone operational tooling. The exploit capability is CPU exhaustion, not code execution. It targets Next.js applications exposing Server Actions backed by vulnerable React Server Components. The attack flow is: identify a Next.js target, extract a valid 40-hex Server Action ID from page source or JS bundles, send a baseline POST request to '/', then send a crafted multipart/form-data POST to '/' with 'Next-Action: <id>' and a malicious Flight payload containing repeated '$Q0' self-references. This abuses Map deserialization behavior to force repeated recomputation with quadratic complexity, causing long response times and effective service unavailability. The Nuclei template performs four phases: (1) GET {{BaseURL}} to fingerprint Next.js via headers/body, (2) GET {{BaseURL}} again to regex-extract createServerReference("<40 hex>") action IDs, (3) POST / with a benign multipart body to establish baseline timing, and (4) POST / with the malicious payload and flag likely vulnerability when response duration is >= 3 seconds and status is one of 200/400/404/500. This makes the template more than passive detection; it actively probes the vulnerable code path with a reduced exploit payload. The Bash script automates action ID extraction by requesting the target root, parsing HTML and Next.js bundle paths under '/_next/static/', and checking common chunk paths. The Python PoC is a fuller operational tool with automation for recon, extraction, detection, exploitation, concurrency, timing/statistics, interrupt handling, and optional JSON reporting. Overall, the repository's purpose is to identify vulnerable Next.js/React deployments and demonstrate or induce denial of service through crafted Flight protocol requests.cybertechajju · Disclosed Apr 11, 2026 · Framework: nuclei · yaml · bash · network · webWeaponized
FAQ

Frequently asked questions

Is CVE-2026-23869 exploited in the wild?
As of Oct 23, 2026, Mallory has no reports of CVE-2026-23869 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-23869?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-23869, the earliest disclosed Apr 11, 2026.
Is there a patch for CVE-2026-23869?
Upgrade all affected React Server Components packages to versions containing the CVE-2026-23869 fix: 19.0.5, 19.1.6, or 19.2.5, according to the release branch. For affected Next.js App Router applications, upgrade 13.x, 14.x, and vulnerable 15.x installations to 15.5.15 or later, and vulnerable 16.x installations to 16.2.3 or later.
How severe is CVE-2026-23869?
CVE-2026-23869 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.6% (76th percentile) as of Oct 23, 2026.
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 activity12Community discussion across Reddit, Mastodon, and other social sources.