CVE-2026-23864: Multiple denial of service vulnerabilities exist in React Server Components, affecting the following packag...
Multiple denial of service vulnerabilities exist in React Server Components, affecting the following packages: react-server-dom-parcel, react-server-dom-turbopack, react-server-dom-webpack.
The vulnerabilities are triggered by sending specially crafted HTTP requests to Server Function endpoints, and could lead to server crashes, out-of-memory exceptions or excessive CPU usage; depending on the vulnerable code path being exercised, the application configuration and application code.
Strongly consider upgrading to the latest package versions to reduce risk and prevent availability issues in applications using React Server Components.
Security readout for executives and security teams
Plain-English summary
This is an availability risk in React Server Components packages. A remote attacker may be able to send crafted HTTP requests to Server Function endpoints and crash the server or exhaust memory or CPU. The issue matters most for internet-facing applications using the affected RSC packages.
Executive priority
Treat as high priority for affected internet-facing RSC applications because the impact is service outage, not data theft. Patch quickly where affected packages are deployed, and validate exposure before broad emergency action.
Technical view
CVE-2026-23864 covers multiple denial-of-service flaws in react-server-dom-webpack, react-server-dom-turbopack, and react-server-dom-parcel versions 19.0.0, 19.1.0, and 19.2.0. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges or user interaction, with high availability impact only.
Likely exposure
Exposure is limited to applications using React Server Components with the affected packages and reachable Server Function endpoints. Do not treat every React application as affected without dependency and runtime validation.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector indicates the issue is remotely reachable without authentication, and the vendor description says crafted HTTP requests can trigger crashes, memory exhaustion, or excessive CPU usage.
Researcher notes
Key uncertainty is application-specific reachability: vulnerable behavior depends on code path, configuration, and application code. Sources identify affected package families and versions, but do not provide exploit details, confirmed exploitation, or universal framework-level impact.
Mitigation direction
Inventory affected React Server Components packages and versions.
Upgrade affected packages to the latest available versions.
Prioritize internet-facing applications with Server Function endpoints.
Review Meta and Red Hat advisories for product-specific remediation.
Monitor application crashes, memory pressure, and CPU saturation.
If upgrade is blocked, follow vendor guidance rather than ad hoc fixes.
Validation and detection
Check package lockfiles and deployed artifacts for affected package versions.
Confirm whether React Server Components and Server Function endpoints are used.
Map exposed routes that reach Server Function handling.
Verify upgraded versions are present in production builds.
Review runtime logs for unexplained crashes or resource exhaustion.
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-1284: 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.
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.
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.
Jan 26, 2026, 19:16 UTC (UTC+00:00)
CVE publishedCVE Program
The CVE record was published.
Jan 26, 2026, 19:16 UTC (UTC+00:00)
ADP timelineredhat-SADP
Reported to Red Hat.
Jan 26, 2026, 20:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Jul 3, 2026, 12:04 UTC (UTC+00:00)
ADP provider summaries
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPreact-server-dom-webpack: react-server-dom-parcel: reactreact-server-dom-turbopack: React Server Components: Denial of Service via specially crafted HTTP requests
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1284 · source CWE mapping
Improper Validation of Specified Quantity in Input
Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.