Ruby patches Ruby2Shell and six other flaws
Ruby 4.0.10, 3.4.13 and 3.3.14 fix seven bugs, including the Ruby2Shell heap overflow in string case conversion. Exploitation looks hard, but patch.

Ruby shipped security releases this week, and the headline item is a heap-based buffer overflow in string case conversion that researchers have named Ruby2Shell. It is tracked as CVE-2026-132825. SecurityWeek reported on November 20 that the fixes cover seven vulnerabilities in total, in the regular expression engine and in string case conversion, and that proof-of-concept code demonstrating remote code execution exists for five of them.
What to do: upgrade to Ruby 4.0.10, 3.4.13 or 3.3.14, depending on your branch. The reporting does not describe any exploitation in the wild.
What is affected
Per SecurityWeek, Ruby2Shell affects case-conversion operations in some single-byte encodings, including ISO-8859-1 and Windows-1252. In affected code, Ruby checks that there is room for one byte but can write two, so adjacent heap memory may be corrupted. The reporting cites Veria Labs as saying that, in default configurations, an unauthenticated attacker could reach the flaw through Rails, classic-style Sinatra and potentially other frameworks. watchTowr’s description is broader: any Ruby application that changes the case of external text in a single-byte encoding is exposed.
Downstream projects are already moving. Veria Labs says GitHub Enterprise Server is affected, while Chatwoot, GitLab, Mastodon, OpenProject and the Discourse base image have patched.
The other six issues include a double free, two integer overflows and another heap-based buffer overflow, all with PoC code demonstrating RCE, plus an out-of-bounds read with a PoC showing memory corruption. SecurityWeek notes that CVE identifiers for those have been requested but not yet assigned. A separate out-of-bounds read in the regex engine can leak memory and crash processes.
How worried to be
Not very, if you patch promptly. watchTowr’s Yordan Ganchev told SecurityWeek that turning this into reliable code execution is difficult: it needs a non-glibc memory allocator, particular runtime configuration and application logic preconditions, and an attacker would still have to defeat ASLR. The more likely outcome of malformed input is a crashed process and a service disruption.
Analysis: “hard to exploit” is a statement about today’s public tooling, not a permanent property. Veria Labs says it plans to release its PoC after major vendors have rolled out patches, and that is the point where the window for stragglers narrows. Anything running Ruby in the single-byte-encoding corner, or a vendored Ruby inside an appliance you do not control, is the sort of deployment that sits unpatched the longest.
Related coverage
- PHP security releases fix critical RCE flaws, another language runtime patch cycle landing the same week.
Found this useful? Share it.

