Case study / Security response
Five customer Rails apps patched in one day
Ruby2Shell (CVE-2026-132825)
Handrail moved every affected customer Rails app it hosts to the fixed Ruby and checked the version actually running in each one.
34 min
Go-ahead to the first production app running the fixed Ruby
4 of 5
Apps live in production within 1 hour 34 minutes of the go-ahead
Same day
All five apps in production on Ruby 3.4.13 by 4:54 PM CT, Nov. 19
The need
Ruby2Shell is a heap overflow in the Ruby interpreter that public research says an unauthenticated attacker can reach in a default Rails app. Ruby shipped the fix in 3.4.13. Five production Rails apps that Handrail hosts for three customers in retail, wholesale and e-commerce were running 3.4.12. Updating gems would not fix it.
What Handrail delivered
Work started at the 11:03 AM go-ahead, after a morning check of the Ruby running in each app. Each app moved to the official Ruby 3.4.13 image, pinned by digest, with no gem upgrades. Four were committed by 11:15 AM and reached production between 11:37 AM and 12:37 PM, each after passing staging. A stuck platform request held up the fifth until the afternoon.
What we could verify
Release records show each app passing staging before production. At 1:17 PM, every web, worker and Sidekiq pod of the first four apps, in staging and production, reported running Ruby 3.4.13. The fifth reached production at 4:54 PM; its three production pods log Ruby 3.4.13 at startup.
Intervals run from the 11:03 AM CT go-ahead to production release completion on Nov. 19, 2026; they exclude earlier triage. Ruby published the fix Nov. 18. No public exploit was out yet; one was expected around Nov. 25. We make no claim that exploitation was attempted or prevented. Customers are anonymized. Evidence: in-pod Ruby runtime checks and Handrail release records.
