Post

The risk here is that you incorrectly assume you’re only using x but don’t realize or forget y is actually used. So please just update, it’s only a patch release and we published it to all impacted minors.

At some point in the future we will share details. For now we are withholding to allow the industry to protect themselves given the severity of the vulnerability

Our thanks to the @react.dev team for informing us so that we could provide mitigation for our users. bsky.app/profile/deno...

Deno@deno.land

Next.js / React Server Components vulnerability identified. Apps deployed on Deno Deploy infrastructure are already protected by a runtime-level patch applied by our team. See this post for more information on how to protect your projects. deno.com/blog/react-s...

RSCs were a mistake. I went back to a client-side only solution using Preact for my latest project because the complexity you buy into is simply not worth the benefit of RSCs.

I'm using pure Preact and have no need for routing. I keep it very minimalistic and use fetch for data loading, and build my own hooks for state management. I also rolled my own i18n solution this time and I'm quite happy so far.

Thank you to the React and Next.js teams for involving us early and for the clear communication. We were able to patch our network ahead of disclosure to help keep our customers secure. bsky.app/profile/netl...

Netlify@netlify.com

A critical vulnerability was recently disclosed in React Server Components (RSC), impacting multiple versions of React, Next.js and other RSC-based frameworks. This flaw could allow malicious actors to execute arbitrary code within an affected application. 🧵