CVE-2026-23864

Published Jan 26, 2026
·
Updated

## Impact It was found that the fixes to address DoS in React Server Components were incomplete and we found multiple denial of service vulnerabilities still exist in React Server Components. We recommend updating immediately. The vulnerability exists in versions 19.0.0, 19.0.1, 19.0.2, 19.0.3, 19.1.0, 19.1.1, 19.1.2, 19.1.3, 19.1.4, 19.2.0, 19.2.1, 19.2.2, 19.2.3 of: - [react-server-dom-webpack](https://www.npmjs.com/package/react-server-dom-webpack) - [react-server-dom-parcel](https://www.npmjs.com/package/react-server-dom-parcel) - [react-server-dom-turbopack](https://www.npmjs.com/package/react-server-dom-turbopack?activeTab=readme) 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. ## Patches Fixes were back ported to versions 19.0.4, 19.1.5, and 19.2.4. If you are using any of the above packages please upgrade to any of the fixed versions immediately. If your app’s React code does not use a server, your app is not affected by this vulnerability. If your app does not use a framework, bundler, or bundler plugin that supports React Server Components, your app is not affected by this vulnerability. ## References See the [blog post](https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components) for more information and upgrade instructions.

Affected Software

15 affected componentsFixes available
npm/react-server-dom-parcel
npm/react-server-dom-turbopack
npm/react-server-dom-webpack
npm/react-server-dom-turbopack>=19.2.0-canary-63779030-20250328<19.2.4
19.2.4
npm/react-server-dom-webpack>=19.0.0<19.0.4
19.0.4
npm/react-server-dom-webpack>=19.1.0-canary-7130d0c6-20241212<19.1.5
19.1.5
npm/react-server-dom-parcel>=19.2.0-canary-63779030-20250328<19.2.4
19.2.4
npm/react-server-dom-parcel>=19.1.0-canary-7130d0c6-20241212<19.1.5
19.1.5
npm/react-server-dom-turbopack>=19.0.0<19.0.4
19.0.4
npm/react-server-dom-webpack>=19.2.0-canary-63779030-20250328<19.2.4
19.2.4
npm/react-server-dom-turbopack>=19.1.0-canary-7130d0c6-20241212<19.1.5
19.1.5
npm/react-server-dom-parcel>=19.0.0<19.0.4
19.0.4
Facebook React>=19.0.0<19.0.4
Facebook React>=19.1.0<19.1.5
Facebook React>=19.2.0<19.2.4

Event History

Jan 26, 2026
CVE Published
via MITRE·07:16 PM
Data Sourced
via MITRE·07:16 PM
DescriptionWeakness
Data Sourced
via Red Hat·08:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
Affected Software
Jan 29, 2026
Advisory Published
via GitHub·03:00 PM
Data Sourced
via GitHub·03:00 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-23864?

CVE-2026-23864 is classified as a denial of service vulnerability.

2

What software packages are affected by CVE-2026-23864?

CVE-2026-23864 affects react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack.

3

How do I fix CVE-2026-23864?

To fix CVE-2026-23864, update the affected packages to their latest versions as recommended by the maintainers.

4

What causes CVE-2026-23864 to be exploited?

CVE-2026-23864 can be exploited by sending specially crafted HTTP requests to Server Function endpoints.

5

Are there any mitigations for CVE-2026-23864?

Yes, implementing input validation on Server Function endpoints can help mitigate the effects of CVE-2026-23864.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203