---
id: "CVE-2026-23870"
kind: "vulnerability"
aliases: ["CVE-2026-23870"]
title: "React Server Components: crafted HTTP requests cause denial of service"
severity: "high"
cvss: 7.5
epss: 0.01533
exploited: false
status: "open"
category: "package"
products: [{"name": "facebook react-server-dom-parcel", "fixed": [], "affected": ">= 19.0.0, <= 19.0.5", "ecosystem": "vendor"}, {"name": "facebook react-server-dom-parcel", "fixed": [], "affected": ">= 19.1.0, <= 19.1.6", "ecosystem": "vendor"}, {"name": "facebook react-server-dom-parcel", "fixed": [], "affected": ">= 19.2.0, <= 19.2.5", "ecosystem": "vendor"}, {"name": "facebook react-server-dom-turbopack", "fixed": [], "affected": ">= 19.0.0, <= 19.0.5", "ecosystem": "vendor"}, {"name": "facebook react-server-dom-turbopack", "fixed": [], "affected": ">= 19.1.0, <= 19.1.6", "ecosystem": "vendor"}, {"name": "facebook react-server-dom-turbopack", "fixed": [], "affected": ">= 19.2.0, <= 19.2.5", "ecosystem": "vendor"}, {"name": "facebook react-server-dom-webpack", "fixed": [], "affected": ">= 19.0.0, <= 19.0.5", "ecosystem": "vendor"}, {"name": "facebook react-server-dom-webpack", "fixed": [], "affected": ">= 19.1.0, <= 19.1.6", "ecosystem": "vendor"}, {"name": "facebook react-server-dom-webpack", "fixed": [], "affected": ">= 19.2.0, <= 19.2.5", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["cloudflare", "cloudflare-workers", "lab-disclosure", "next.js", "package", "react", "self-hosted"]
not_affected_if: ["no-server-components", "static-export"]
published_at: "2026-05-06T17:16:22+00:00"
first_seen_at: "2026-10-24T18:56:54+00:00"
updated_at: "2026-10-25T12:38:49+00:00"
sources: [{"source": "lab", "url": "https://developers.cloudflare.com/changelog/post/2026-05-06-react-nextjs-vulnerabilities/", "first_seen_at": "2026-10-24T18:56:54+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23870", "first_seen_at": "2026-10-24T19:23:38+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-23870", "first_seen_at": "2026-10-25T12:38:49+00:00"}]
---

# React Server Components: crafted HTTP requests cause denial of service

Specially crafted HTTP requests sent to React Server Components server functions can crash or stall the server process. An unauthenticated attacker can take the affected application offline.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:facebook react-server-dom-parcel affected >= 19.0.0, <= 19.0.5 fixed ?
- vendor:facebook react-server-dom-parcel affected >= 19.1.0, <= 19.1.6 fixed ?
- vendor:facebook react-server-dom-parcel affected >= 19.2.0, <= 19.2.5 fixed ?
- vendor:facebook react-server-dom-turbopack affected >= 19.0.0, <= 19.0.5 fixed ?
- vendor:facebook react-server-dom-turbopack affected >= 19.1.0, <= 19.1.6 fixed ?
- vendor:facebook react-server-dom-turbopack affected >= 19.2.0, <= 19.2.5 fixed ?
- vendor:facebook react-server-dom-webpack affected >= 19.0.0, <= 19.0.5 fixed ?
- vendor:facebook react-server-dom-webpack affected >= 19.1.0, <= 19.1.6 fixed ?
- vendor:facebook react-server-dom-webpack affected >= 19.2.0, <= 19.2.5 fixed ?

## How to check

- Check installed versions with `npm ls react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack`
- Check the Next.js version with `npm ls next`; Next.js is affected below `15.5.16` and `16.2.5`
- Look for these packages in `package.json` and lockfiles if the app does not use them directly

## Fix

- Upgrade `react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` to `19.0.6`, `19.1.7`, or `19.2.6` on the matching release line
- Upgrade Next.js to `15.5.16` or `16.2.5`
- Cloudflare WAF managed rules block related RSC attack patterns, but Cloudflare says they are not a full fix; update the packages

## Timeline

- 2026-10-24T18:56:54+00:00 lab https://developers.cloudflare.com/changelog/post/2026-05-06-react-nextjs-vulnerabilities/ — Cloudflare: WAF and framework adapter mitigations for React and Next.js vulnerabilities · Changelog
- 2026-10-24T19:23:38+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-23870
- 2026-10-25T12:38:49+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-23870

## Documents

- [advisory] Cloudflare: WAF and framework adapter mitigations for React and Next.js vulnerabilities · Changelog https://developers.cloudflare.com/changelog/post/2026-05-06-react-nextjs-vulnerabilities/

## From the sources

WAF and framework adapter mitigations for React and Next.js vulnerabilities · Changelog

# Changelog

New updates and improvements at Cloudflare.

May 7, 2026

## WAF and framework adapter mitigations for React and Next.js vulnerabilities

Multiple security vulnerabilities were disclosed by the React team and Vercel affecting React Server Components and Next.js. These include denial of service, middleware and proxy bypass, server-side request forgery, cross-site scripting, and cache poisoning issues across a range of severity levels.

We strongly recommend updating your application and its dependencies immediately. Patched versions are available for React (`react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` `19.0.6`, `19.1.7`, and `19.2.6`) and Next.js (`15.5.16` and `16.2.5`).

#### WAF protections

Cloudflare WAF rules deployed in response to prior React Server Component CVEs (`CVE-2025-55184` ↗︎ and `CVE-2026-23864` ↗︎) already provide coverage for the newly disclosed denial-of-service vulnerabilities. These rules are enabled by default with a Block action for all customers using the Cloudflare Managed Ruleset, including Free plan customers using the Free Managed Ruleset.

| Ruleset | Rule description | Rule ID | Default action |
| --- | --- | --- | --- |
| Cloudflare Managed Ruleset | React - DoS - `CVE-2025-55184` ↗︎ | `2694f1610c0b471393b21aef102ec699` | Disabled |
| Cloudflare Managed Ruleset | React - DoS - `CVE-2026-23864` ↗︎ | `aaede80b4d414dc89c443cea61680354` | Block |

The existing rules detect the underlying attack patterns generically. As a result, they apply to the new `CVE-2026-23870` ↗︎ denial-of-service vulnerability in Server Components and the corresponding Next.js advisory `GHSA-8h8q-6873-q5fj` ↗︎.

Cloudflare is investigating whether WAF rules can be safely and effectively deployed for three of the high-severity advisories: `CVE-2026-23870` ↗︎ / `GHSA-8h8q-6873-q5fj` ↗︎, `GHSA-267c-6grr-h53f` ↗︎, and `GHSA-mg66-mrh9-m8jx` ↗︎. If it is possible to create a managed WAF rule that mitigates these CVEs and does not potentially break application behavior, Cloudflare will add additional managed WAF rules. These rules will be announced through the WAF changelog. Because these vulnerabilities were shared with Cloudflare with minimal advance notice, we are still investigating what WAF mitigations are possible.

Several of the disclosed vulnerabilities are not possible to block in WAF. We strongly recommend updating your applications so they are not purely reliant on WAF mitigations.

Customers on Pro, Business, or Enterprise plans should ensure that Managed Rules are enabled.

#### Next.js adapters

Vinext: Vinext ↗︎ is a Vite plugin that reimplements the Next.js API surface. Vinext's latest release is not vulnerable to any of the disclosed CVEs. Vinext's architecture differs from stock Next.js in ways that sidestep the affected code paths. For example, it does not implement the PPR resume protocol, does not expose Pages Router data-route endpoints, and strips internal headers such as `x-nextjs-data` at request boundaries. As an extra layer of defense, we added a React `19.2.6` or later requirement when running `vinext init` (PR #1118 ↗︎, PR #1112 ↗︎) to prevent accidentally running a vulnerable version of React with Vinext.

OpenNext on Cloudflare: OpenNext is an adapter that lets you deploy Next.js apps to the Cloudflare Workers platform. OpenNext itself is not directly vulnerable to the React denial-of-service CVE, but users must update the Next.js version in their application. The OpenNext team has updated the adapter to further harden against these vectors and released a new version of the Cloudflare adapter. Test fixtures and examples have been updated to use patched versions (PR #1255 ↗︎).

#### Summary of disclosed vulnerabilities

| Advisory | Severity | Issue | WAF status |
| --- | --- | --- | --- |
| `CVE-2026-23870` ↗︎ / `GHSA-8h8q-6873-q5fj` ↗︎ | High | Denial of service in Server Components | WAF rules in place: `2694f1610c0b471393b21aef102ec699`, `aaede80b4d414dc89c443cea61680354` Cloudflare is investigating additional managed WAF coverage |
| `GHSA-267c-6grr-h53f` ↗︎ | High | Middleware bypass via segment-prefetch routes | Cloudflare is investigating if this can be safely and effectively mitigated by a managed WAF rule |
| `GHSA-mg66-mrh9-m8jx` ↗︎ | High | Denial of service via connection exhaustion in Cache Components | Cloudflare is investigating if this can be safely and effectively mitigated by a managed WAF rule |
| `GHSA-492v-c6pp-mqqv` ↗︎ | High | Middleware bypass via dynamic route parameter injection | Not possible to safely enable a managed WAF rule without potentially breaking application behavior |
| `GHSA-c4j6-fc7j-m34r` ↗︎ | High | SSRF via WebSocket upgrades | Not possible to safely enable a managed WAF rule without potentially breaking application behavior |
| `GHSA-36qx-fr4f-26g5` ↗︎ | High | Middleware bypass in Pages Router i18n | Custom WAF rule possible; global managed rule could potentially break application behavior |
| `GHSA-ffhc-5mcf-pf4q` ↗︎ | Moderate | XSS via CSP nonces | Custom WAF rule possible; global managed rule could potentially break application behavior |
| `GHSA-gx5p-jg67-6x7h` ↗︎ | Moderate | XSS in `beforeInteractive` scripts | Not possible to safely enable a managed WAF rule without potentially breaking application behavior |
| `GHSA-h64f-5h5j-jqjh` ↗︎ | Moderate | Denial of service in Image Optimization API | Custom WAF rule possible; global managed rule could potentially break application behavior |
| `GHSA-wfc6-r584-vfw7` ↗︎ | Moderate | Cache poisoning in RSC responses | Custom WAF rule possible; global managed rule could potentially break application behavior |
| `GHSA-vfv6-92ff-j949` ↗︎ | Low | Cache poisoning via RSC cache-busting collisions | Not possible to safely enable a managed WAF rule without potentially breaking application behavior |
| `GHSA-3g8h-86w9-wvmq` ↗︎ | Low | Middleware redirect cache poisoning | Custom WAF rule possible; global managed rule could potentially break application behavior |

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_