Navigate Select ESC Close

React got hacked. It's really, really bad.

2025-12-08 Science & Technology
112.4k
3.5k
420
Theo - t3․gg
Theo - t3․gg
539.0k subscribers

Unlock all features

FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.

Description

Yes, React actually got hacked... Thank you WorkOS for sponsoring! Check them out at: https://soydev.link/workos SOURCES https://x.com/rauchg/status/1997362942929440937 https://x.com/duborges/status/1997293892090183772 https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components https://blog.cloudflare.com/5-december-2025-outage/ Want to sponsor a video? Learn more here: https://soydev.link/sponsor-me Check out my Twitch, Twitter, Discord more at https://t3.gg S/O Ph4se0n3 for the awesome edit 🙏

Top Comments (10)

@aaronevans7713 2025-12-09

The impressive part is that anyone was actually able to use React Server Components at all.

482 11 replies
@victorbjorklund 2025-12-08

me last week: shit we are really behind using nextjs 14. Me this week: thank god we are using nextjs 14

474 10 replies
@Sierra097 2025-12-08

I'd love to update. I'm scared of NPM at this point 😂

190 4 replies
@kspworks 2025-12-08

Too bad that my company's production server was hacked 2 days ago because of this... 🤷‍♂

150 5 replies
@FireStormOOO_ 2025-12-08

I think this is an example of building something so clever it was hard to realize the security implications in advance. It is an elaborate mechanism for taking code (or arbitrarily complex state that functionally also qualifies as code security-wise) from the client and running it on the server, but that's not what it sounds like at first glance and I've never heard anyone talk about server components the same way we talk about the browser sandbox being security critical. That does actually seem like a developer education mistake we're making in multiple platforms.

142 14 replies
@ObenjOne 2025-12-09

Ah shoot. Why did I have to watch this after midnight? Now I gotta get up and check if I’ve been hacked Edit: Yep, I was hacked D:

123 2 replies
@ymi_yugy3133 2025-12-08

31:58 "There is something like this in almost every complex enough codebase" This completely misses the point. I could find only one notable, somewhat recent CVE (2018-6341) in React prior to this. Discovered in 2018 an XSS attack on ReactDOMServer with a CVSS of 6.1. The lesson isn't "every big project has security vulnerabilities" (though it's true) it's "overly complex wire transfer formats are dangerous, especially when parsed by dynamic languages". For example, the most critical vulnerabilities in gRPC were caused either by C memory bugs or JS prototype pollution.

94 3 replies
@OS-Advertising 2025-12-09

the dev that discovered and reported this should immediately get an offer from meta higher then his current salary

90
@nekomakhea9440 2025-12-08

>Credit to the dev that disclosed this, he could have done terrible things Or sold the exploit to intel agencies for a ffffffuck ton of money

45 3 replies
@om98357 2025-12-09

18:55 correction: just because it was not 'publicly' known and exploited does not mean it was not privately known and exploited - SREs will have to go back in their logs and check if this was actually utilized before

32

Unlock the Data Inside
Turn Videos into Knowledge

  • Get FREE 10/day: transcripts, summaries, chats
  • Chat with videos, export text & PDF
  • $1 free API credit for RAG, chatbots & research

Free forever plan • All features unlocked

App screenshot