CVE-2026-23869
HIGHCVE-2026-23869 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in react-server-dom-parcel. O3 Security confirms whether CVE-2026-23869 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
React Server Components have a Denial of Service Vulnerability
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
react-server-dom-parcelnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-server-dom-parcel | ≥ 19.0.0&&< 19.0.5 | 19.0.5 |
| 📦npm | react-server-dom-parcel | ≥ 19.1.0&&< 19.1.6 | 19.1.6 |
| 📦npm | react-server-dom-parcel | ≥ 19.2.0&&< 19.2.5 | 19.2.5 |
| 📦npm | react-server-dom-turbopack | ≥ 19.0.0&&< 19.0.5 | 19.0.5 |
| 📦npm | react-server-dom-turbopack | ≥ 19.1.0&&< 19.1.6 | 19.1.6 |
| 📦npm | react-server-dom-turbopack | ≥ 19.2.0&&< 19.2.5 | 19.2.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-server-dom-parcel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update react-server-dom-parcel to 19.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-23869 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-23869 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-23869. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-23869 in your dependencies?
O3 detects CVE-2026-23869 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.