The RCE that asked nothing of you
In December 2025 React2Shell landed (CVE-2025-55182, CVSS 10.0, and the corresponding CVE-2025-66478 in Next.js): unauthenticated remote code execution in React Server Components, via insecure deserialization. The detail that made headlines: a default app created with create-next-app and built for production was already exploitable, with no code changes from the developer. Real in-the-wild exploitation started on December 5, mostly dropping crypto miners on hit servers.
Read that again: you could have done everything right, followed the official tutorial, and still have a 10.0 RCE on your server, just by running the vulnerable version in production.
Why it breaks the founder's intuition
The intuition of someone building with AI is: "I used the most popular framework, the default way, so I am safe". React2Shell buries that intuition. The flaw was not in a wrong line you wrote; it was in how the framework deserialized input. Popularity and "default" are not security properties.
That has a direct practical consequence: keeping the framework and runtime updated stopped being maintenance hygiene and became a front-line security control. A SaaS that goes months without updating Next.js is not just "outdated"; it is potentially sitting on a known, exploited RCE.
What to do
- Update framework and runtime as a security priority, not when there is spare time. React2Shell's fix came as a patch; applying it was the urgent step.
- In your code, never deserialize untrusted data into an arbitrary type. Accept input as pure data (schema-validated JSON), not as an object that reconstructs types.
- Run the app with least privilege, to limit what an RCE reaches if it happens (the miner only ran because the process had permission to).
- Monitor your version against known-CVE advisories (SCA + tracking), so you do not find out late.
The angle RET covers
React2Shell is the framework's, but the blast radius is yours: if an RCE happens, what it reaches (secrets, database, other customers' data) depends on how YOU built the app. RET's Risk Review maps that blast radius and reviews where your code deserializes input and with what privilege it runs. Updating closes today's CVE; limiting the radius protects you from the next one.
"Default" and "popular" are not security. Keeping the framework updated is a front-line control, and limiting the blast radius is what protects you from the RCE that does not have a name yet.
