CVE-2026-23869: A denial of service vulnerability exists in React Server Components, affecting the following packages: reac...
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.
Security readout for executives and security teams
Plain-English summary
This CVE can let an unauthenticated remote requester tie up CPU on affected React Server Components server-function endpoints. The reported impact is denial of service, not data theft or code execution. Business urgency depends on whether affected React server packages are deployed on externally reachable services.
Executive priority
Treat this as a high-priority availability risk for internet-facing React Server Components applications. It does not indicate data compromise, but a simple unauthenticated request pattern could degrade service capacity where affected endpoints are reachable.
Technical view
CVE-2026-23869 affects react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack in listed 19.x ranges. Specially crafted HTTP requests to Server Function endpoints can cause excessive CPU use for up to a minute before a catchable error. CVSS 3.1 is 7.5, driven by network reachability and high availability impact.
Likely exposure
Likely exposed systems are applications using the affected React Server Components packages and versions with Server Function endpoints reachable over HTTP. Services not using these packages, not in the affected ranges, or without reachable Server Function endpoints are less likely exposed.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is described as low-complexity, unauthenticated, network-triggered denial of service, so internet-facing endpoints should be treated as operationally significant even without exploitation evidence.
Researcher notes
Evidence is strongest for affected package ranges, trigger class, and availability impact. Public source details do not provide exploit status, proof-of-concept behavior, or a specific patch version in the supplied bundle, so validation should focus on dependency range and endpoint exposure.
Mitigation direction
Inventory React Server Components packages and versions across production applications.
Prioritize externally reachable Server Function endpoints using affected package ranges.
Move affected packages to vendor-supported releases outside affected ranges, following React advisory guidance.
Apply rate limiting or request controls where server-function endpoints are exposed.
Monitor CPU saturation, request spikes, and repeated server-function errors.
Validation and detection
Check dependency manifests and lockfiles for the affected package names and versions.
Map which applications expose React Server Function endpoints over HTTP.
Confirm deployed artifacts match reviewed dependency versions, not only source repositories.
Review logs and metrics for unusual CPU spikes tied to server-function routes.
Track React, CVE Program, and Red Hat advisories for updated remediation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
ADP timelineredhat-SADP
Made public.
Apr 8, 2026, 19:11 UTC (UTC+00:00)
CVE publishedCVE Program
The CVE record was published.
Apr 8, 2026, 19:11 UTC (UTC+00:00)
ADP timelineredhat-SADP
Reported to Red Hat.
Apr 8, 2026, 20:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Jul 15, 2026, 01:17 UTC (UTC+00:00)
ADP provider summaries
CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPreact-server-dom-parcel: react-server-dom-turbopack: react-server-dom-webpack: denial of service via specially crafted HTTP requests to Server Function endpoints