cve.bz

CVE-2026-23869 (React2DoS) meta: Uncontrolled Resource Consumption

7.5 highEPSS 1.6%Fix available

Known as React2DoS

High (7.5) in meta. EPSS 1.6% estimated probability of exploitation activity in the next 30 days. Fixed in react-server-dom-parcel 19.0.5, 19.1.6, 19.2.5.

On this page
A denial of service vulnerability exists in React Server Components, affecting the following packages: react-server-dom-parcel, react-server-dom-turbopack and react-server-dom-webpack (versions 19.0.0 through 19.0.4, 19.1.0 through 19.1.5, and 19.2.0 through 19.2.4). The vulnerability is triggered by sending specially crafted HTTP requests to Server Function endpoints.The payload of the HTTP request causes excessive CPU usage for up to a minute ending in a thrown error that is catchable.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
1.6% (unchanged from 1.6% a week ago; 1.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 76th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-04-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-502 Deserialization of Untrusted Data
CWE-770 Allocation of Resources Without Limits or Throttling
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • react-server-dom-parcel (npm): fixed in 19.0.5, 19.1.6, 19.2.5
  • react-server-dom-turbopack (npm): fixed in 19.0.5, 19.1.6, 19.2.5
  • react-server-dom-webpack (npm): fixed in 19.0.5, 19.1.6, 19.2.5

Ask an AI about this CVE

Show the promptExplain CVE-2026-23869 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-23869?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-23869?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-23869 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Meta react-server-dom-turbopackfrom 19.0.0 through 19.0.4
Meta react-server-dom-turbopackfrom 19.1.0 through 19.1.5
Meta react-server-dom-turbopackfrom 19.2.0 through 19.2.4
Meta react-server-dom-parcelfrom 19.0.0 through 19.0.4
Meta react-server-dom-parcelfrom 19.1.0 through 19.1.5
Meta react-server-dom-parcelfrom 19.2.0 through 19.2.4
Meta react-server-dom-webpackfrom 19.0.0 through 19.0.4
Meta react-server-dom-webpackfrom 19.1.0 through 19.1.5
Meta react-server-dom-webpackfrom 19.2.0 through 19.2.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-479c-33wc-g2pgnpmreact-server-dom-parcel>=19.0.0 <19.0.519.0.5
GHSA-479c-33wc-g2pgnpmreact-server-dom-parcel>=19.1.0 <19.1.619.1.6
GHSA-479c-33wc-g2pgnpmreact-server-dom-parcel>=19.2.0 <19.2.519.2.5
GHSA-479c-33wc-g2pgnpmreact-server-dom-turbopack>=19.0.0 <19.0.519.0.5
GHSA-479c-33wc-g2pgnpmreact-server-dom-turbopack>=19.1.0 <19.1.619.1.6
GHSA-479c-33wc-g2pgnpmreact-server-dom-turbopack>=19.2.0 <19.2.519.2.5
GHSA-479c-33wc-g2pgnpmreact-server-dom-webpack>=19.0.0 <19.0.519.0.5
GHSA-479c-33wc-g2pgnpmreact-server-dom-webpack>=19.1.0 <19.1.619.1.6
GHSA-479c-33wc-g2pgnpmreact-server-dom-webpack>=19.2.0 <19.2.519.2.5

Red Hat

Red Hat rates this Important.

Red Hat's statement

Applications are not vulnerable to this issue if they do not use a server, or if they do not use a framework, bundler, or plugin that supports React server components.

This vulnerability allows an unauthenticated remote attacker to cause a denial of service. Due to these reasons, this flaw has been rated with an important severity.

Red Hat's mitigation

Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-dashboard-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-23869.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High
  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON