Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →React shipped fixes on November 10, 2026 for an unauthenticated remote code execution flaw in Server Components' Flight protocol — and the advisory's own scope sentence is the most important part of the story. That is CVE-2026-126187: a deserialization flaw (CWE-502) in the react-server-dom-* packages, scored CVSS v4 9.5, that in the cases it reaches lets a visitor with no account execute code on the server. This write-up carries the catch unburied, because the catch decides whether you need to drop everything or just schedule the upgrade.
CVE-2026-126187 is an unauthenticated remote code execution vulnerability in React Server Components, disclosed November 10, 2026 (CNA: GitHub; the CVE record was published November 10, 2026 and updated November 13, 2026).
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N. Network-reachable, no privileges and no user interaction required.react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack at 19.0.0–19.0.8, 19.1.0–19.1.9, 19.2.0–19.2.8, and 19.3.0.Check package.json and your lockfile — not your deployed pages. You are in the affected set if your project depends on react-server-dom-webpack, react-server-dom-parcel or react-server-dom-turbopack in one of the affected ranges above and your app actually runs React Server Components on a server. A purely static React site, or a React app with no server component in play, is outside the advisory's scope — and even among server apps, the record limits the reachable cases to the extremely rare typed-array pattern quoted above.
One honesty note, because it is the whole point of how we cover these: we can't version-check this one from the outside. A deployed app's react-server-dom package version is not passively observable from the live site without guessing at bundle internals, so a URL scan cannot honestly tell you whether you run an affected version — and we will not claim a site is vulnerable to this CVE from a passive web read. Your lockfile is the crime scene here: it names the exact package version, and it is where this question gets answered. What the free mini-scan can do is check the rest of your deployed app's exposed surface while you handle this one in the repo.
package.json, package-lock.json, yarn.lock or pnpm-lock.yaml for the three react-server-dom-* packages and note the resolved versions.Deserialization protocols are attack surface even when they present as "just" data transport. The Flight protocol moves structured values between server and client, and anything that reconstructs objects from wire data inherits the obligations of a parser facing the internet: assume the payload is hostile, because one day it will be. Framework defaults protect the common case; the long tail of typed values is exactly where that protection thins out.
Related: Vibe-Coded App Security Patterns — the recurring failure shapes behind findings like this one. How to Check If Your Web App Is Hacked — the follow-up pass if a repo review finds something you can't explain.
Shipping React Server Components? Check your lockfile against the ranges above, upgrade to the fixed line, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.
The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.
New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.
Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report