CVE-2025-55182: Frequently Asked Questions About React2Shell: React Server Components Remote Code Execution Vulnerability
www.tenable.com
React2Shell: A critical React flaw allowing unauthenticated RCE. Impacts include Next.js, React Router, and apps using Server Components.

I got an email from Vercel urging to upgrade Next.js based project 3 days ago. POC was published 2 days ago. Today I’ve checked my logs and I could already see attack attempts.

    • PortNull@lemmy.dbzer0.com
      8·
      5 days ago

      Are we still vulnerable if our app doesn’t use React Server Functions endpoints?

      Potentially. According to the React Team, even if React Server Functions are not in-use, the vulnerability is still exploitable if React Server Components are supported.

      • TehPers@beehaw.orgEnglish
        5·
        5 days ago

        I think their point was that CSR-only sites would be unaffected, which should be true. Exploiting it on a static site, for example, couldn’t be RCE because the untrusted code is only being executed on the client side (and therefore is not remote).

        Now, most people use, or at least are recommended to use, SSR/RSC these days. Many frameworks make SSR enabled by default. But using raw React with no Next.js, react-router, etc. to create a client-side only site does likely protect you from this vulnerability.

    • melfie@lemy.lol
      2·
      5 days ago

      I typically use React with only CSR, since I’m normally building apps with it over more static websites. Frameworks with SSR are popular, but there’s nothing wrong with an app that downloads and caches itself with a Service Worker when said app has a lot of interactivity and is likely to be used more than once.