CVE-2026-23869 json
React Server Components have a Denial of Service Vulnerability
published 2026-04-08 7 mo ago modified 2026-09-10 59 d ago also EUVD-2026-20584 , GHSA-479c-33wc-g2pg , GHSA-q4gf-8mx6-v5v3
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm react-server-dom-parcel 19.0.5, 19.1.6, 19.2.5
- npm react-server-dom-turbopack 19.0.5, 19.1.6, 19.2.5
- npm react-server-dom-webpack 19.0.5, 19.1.6, 19.2.5
- npm next 15.5.15, 16.2.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-23869 updated cvss 7.5
react-server-dom-parcel: react-server-dom-turbopack: react-server-dom-webpack: denial of service via specially crafted HTTP requests to Server Function endpoints
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-dashboard-rhel9not affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | react-server-dom-parcel | >=19.0.0, <19.0.5 >=19.1.0, <19.1.6 >=19.2.0, <19.2.5 |
19.0.5 19.1.6 19.2.5 |
| npm | react-server-dom-turbopack | >=19.0.0, <19.0.5 >=19.1.0, <19.1.6 >=19.2.0, <19.2.5 |
19.0.5 19.1.6 19.2.5 |
| npm | react-server-dom-webpack | >=19.0.0, <19.0.5 >=19.1.0, <19.1.6 >=19.2.0, <19.2.5 |
19.0.5 19.1.6 19.2.5 |
| npm | next | >=13.0.0, <15.5.15 >=16.0.0-beta.0, <16.2.3 |
15.5.15 16.2.3 |
Affected products
- Meta react-server-dom-turbopack
- Meta react-server-dom-parcel
- Meta react-server-dom-webpack
- Red Hat Red Hat OpenShift AI (RHOAI)
Classification
- Weakness
- Technology feeds
References
-
github.com
/facebook/react/security/advisories/GHSA-479c-33wc-g2pg
web
-
access.redhat.com
/security/cve/CVE-2026-23869
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2456663
issue-tracking
- security.access.redhat.com /data/csaf/v2/vex/2026/cve-2026-23869.json
-
nvd.nist.gov
/vuln/detail/CVE-2026-23869
advisory
-
github.com
/facebook/react
package
-
react.dev
/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components
web
-
github.com
/vercel/next.js/security/advisories/GHSA-q4gf-8mx6-v5v3
web, advisory
-
github.com
/vercel/next.js
package
-
vercel.com
/changelog/summary-of-cve-2026-23869
web
-
github.com
/react/react/security/advisories/GHSA-479c-33wc-g2pg
advisory
Sources
- CVE List CVE-2026-23869
- GitHub Advisory GHSA-479c-33wc-g2pg
- GitHub Advisory GHSA-q4gf-8mx6-v5v3
- NVD CVE-2026-23869
- Maintainer advisory GHSA-479c-33wc-g2pg
- Maintainer advisory GHSA-q4gf-8mx6-v5v3
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of react/react published their own advisory on GitHub. Reviewed sources take precedence over it.