64
React2Shell: maximum severity vulnerability discovered in React
(www.tenable.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Dec 2025
64 points (94.4% liked)
Programming
28304 readers
444 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Well, Element seems to still be running at the unupdated version even after update, so I'm just shutting the server down.
I'm bummed that it took me 5 days to learn about it, does anyone have some tips how to get early warnings for techs you're using? I'm guessing there's a way with npm.
Also, anyone has some tips how to properly compromise-check your server? I'm guessing there are logs to check for compromise, and audit your startup scripts for persistence? Any tools that could help with that?
Renovate can flag CVEs in its pull requests, if you just want to check versions