Multiple denial of service vulnerabilities exist in React Server Components, affecting the following packages: react-server-dom-parcel, reac
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.
- Published
- Jan 26, 2026
- Updated
- Jul 15, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-400
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| react | cpe:2.3:a:facebook:react |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- facebook react19.0.0 and later · before 19.0.4
- facebook react19.1.0 and later · before 19.1.5
- facebook react19.2.0 and later · before 19.2.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Meta). Independent of NVD's CPE analysis and usually ahead of it.
Meta react-server-dom-parcel
- 19.0.0 and later · before 19.0.4affected · semver
- 19.1.0 and later · before 19.1.5affected · semver
- 19.2.0 and later · before 19.2.4affected · semver
Meta react-server-dom-turbopack
- 19.0.0 and later · before 19.0.4affected · semver
- 19.1.0 and later · before 19.1.5affected · semver
- 19.2.0 and later · before 19.2.4affected · semver
Meta react-server-dom-webpack
- 19.0.0 and later · before 19.0.4affected · semver
- 19.1.0 and later · before 19.1.5affected · semver
- 19.2.0 and later · before 19.2.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | react-server-dom-parcel | from 19.0.0 · before 19.0.4 | 19.0.4 |
| npm | react-server-dom-parcel | from 19.1.0-canary-7130d0c6-20241212 · before 19.1.5 | 19.1.5 |
| npm | react-server-dom-parcel | from 19.2.0-canary-63779030-20250328 · before 19.2.4 | 19.2.4 |
| npm | react-server-dom-turbopack | from 19.0.0 · before 19.0.4 | 19.0.4 |
| npm | react-server-dom-turbopack | from 19.1.0-canary-7130d0c6-20241212 · before 19.1.5 | 19.1.5 |
| npm | react-server-dom-turbopack | from 19.2.0-canary-63779030-20250328 · before 19.2.4 | 19.2.4 |
| npm | react-server-dom-webpack | from 19.0.0 · before 19.0.4 | 19.0.4 |
| npm | react-server-dom-webpack | from 19.1.0-canary-7130d0c6-20241212 · before 19.1.5 | 19.1.5 |
| npm | react-server-dom-webpack | from 19.2.0-canary-63779030-20250328 · before 19.2.4 | 19.2.4 |
Same product
facebook: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-55182A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 incluKEV100Now
- CVE-2025-55184A pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.50Plan
- CVE-2025-67779It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attac36Monitor
- CVE-2018-6341React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attribute names at render-time.25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Meta react-server-dom-parcel | 19.0.4 | Vendor (CNA) |
| Meta react-server-dom-parcel | 19.1.5 | Vendor (CNA) |
| Meta react-server-dom-parcel | 19.2.4 | Vendor (CNA) |
| Meta react-server-dom-turbopack | 19.0.4 | Vendor (CNA) |
| Meta react-server-dom-turbopack | 19.1.5 | Vendor (CNA) |
| Meta react-server-dom-turbopack | 19.2.4 | Vendor (CNA) |
| Meta react-server-dom-webpack | 19.0.4 | Vendor (CNA) |
| Meta react-server-dom-webpack | 19.1.5 | Vendor (CNA) |
| Meta react-server-dom-webpack | 19.2.4 | Vendor (CNA) |
| npm:react-server-dom-parcel | 19.0.4 | Package registry (OSV) |
| npm:react-server-dom-parcel | 19.1.5 | Package registry (OSV) |
| npm:react-server-dom-parcel | 19.2.4 | Package registry (OSV) |
| npm:react-server-dom-turbopack | 19.0.4 | Package registry (OSV) |
| npm:react-server-dom-turbopack | 19.1.5 | Package registry (OSV) |
| npm:react-server-dom-turbopack | 19.2.4 | Package registry (OSV) |
| npm:react-server-dom-webpack | 19.0.4 | Package registry (OSV) |
| npm:react-server-dom-webpack | 19.1.5 | Package registry (OSV) |
| npm:react-server-dom-webpack | 19.2.4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.facebook.com/security/advisories/cve-2026-23864
- access.redhat.com/errata/RHSA-2026:13571
- access.redhat.com/errata/RHSA-2026:34608
- access.redhat.com/security/cve/CVE-2026-23864
- bugzilla.redhat.com/show_bug.cgi?id=2433059
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23864.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.