Ruby2Shell (CVE-2026-132825) in 72 hours: find every Ruby runtime including the ones vendors bundle, patch internet-facing Rails and Sinatra first, and watch for crashes before the Nov 25 PoC
For teams running Ruby apps or self-hosted products that ship their own Ruby (GitLab, GitHub Enterprise Server, Mastodon, Discourse, OpenProject, Chatwoot). Default Rails and classic Sinatra reach the bug before authentication.
Inventory Ruby
Bundled runtimes are the ones people miss.
- Find system and app Ruby: ruby -v on hosts, Ruby base images in your registries and Dockerfiles, rbenv/asdf/rvm installs
- List self-hosted products with embedded Ruby and their versions (GitLab, GHES, Mastodon, Discourse, OpenProject, Chatwoot, Chef, Puppet)
- Mark which ones are reachable from the internet
Patch in exposure order
Fixed: Ruby 3.3.14, 3.4.13, 4.0.10.
- Internet-facing Rails/Sinatra apps first, then internal apps
- Self-hosted GitLab to 19.6.1, 19.5.8 or 19.4.10; Mastodon 4.7.6/4.6.12/4.5.22/4.4.29; rebuild Discourse Docker installs
- Restart every Ruby process including Sidekiq/background workers, and rebuild container images
- Move apps on Ruby 3.2 or older to a supported series
Shield what you can't patch yet
GitHub Enterprise Server had no fix at disclosure.
- Put a WAF rule in front that blocks multipart _method parts with a charset parameter or long values
- Restrict GHES and other unpatched products to VPN or allowlisted IPs until the vendor ships a fix
- Make sure origins only accept traffic through the WAF
Detect
Exploit attempts that fail usually crash a worker.
- Alert on Ruby worker segfaults and restart spikes
- Alert on Ruby processes spawning shells or making new outbound connections
- Review logs back to Nov 19 once the PoC is public on or after Nov 25
Close out
Prove it's done.
- Re-scan images and hosts for vulnerable Ruby versions (check distro package releases, which may backport fixes)
- Record products still waiting on vendor fixes and recheck daily