Skip to content- Sources: advisory, writeup, discussion
- Summary: The advisory, CVE-2026-23870, states only that specially crafted HTTP requests to server function endpoints can cause out-of-memory exceptions or excessive CPU usage, and it names react-server-dom-webpack, react-server-dom-turbopack and react-server-dom-parcel at >= 19.0.0 < 19.0.6, >= 19.1.0 < 19.1.7 and >= 19.2.0 < 19.2.6. The mechanism comes from the researcher writeup rather than the advisory: a crafted request makes the server rebuild form data in a loop that blocks the event loop, and the only input needed is a server action ID that the app prints in its own page HTML. The writeup measures about 4 seconds of freeze per request on a plain production build and about 10 seconds per request on a production-shaped setup, with three consecutive requests causing the fronting load balancer to drop the server from rotation and serve 503s to unrelated users.
- Why it matters: The writeup states the rebuild runs before any login, CSRF or origin check, so an app on an affected version with at least one server action anywhere it can be reached gains nothing from its own auth configuration.
- Follow-up: Track whether React publishes a separate notice for the three fixed react-server-dom releases, given the fix shipped as a quiet backport.