- Orca Security reports a one-byte heap overflow in Ruby's string case conversion, CVE-2026-132825, fixed in Ruby 3.3.14, 3.4.13 and 4.0.10.
- The flaw is in the interpreter, not a gem, so bundle update does not address it. Self-hosted products that bundle Ruby need vendor updates.
- Teams should inventory every Ruby runtime, including containers, and prioritise internet-facing Rails and Sinatra apps. Orca reports no exploitation in the wild yet.
The fix lives below the layer most teams watch
Most patch routines track the packages an application imports. This flaw is in the interpreter that runs them. Orca Security reports that CVE-2026-132825, nicknamed "ruby2ßhell", is a heap buffer overflow in Ruby's string case conversion. A heap buffer overflow means a program writes data past the end of a block of memory.
The lesson is simple. A team can keep every gem current and still carry the bug. The problem sits under the application, not inside it.
What the Ruby team has said
Ruby's core team shipped fixed versions on November 18, 2026. They are Ruby 3.3.14, 3.4.13 and 4.0.10. The team rates the issue critical.
The team also says it knows of working exploits that can run attacker code in some situations. Those exploits have not been published.
The researchers behind the original write-up say the faulty code dates back to Ruby 2.4.0. They say they will release their own proof of concept roughly a week after disclosure. Orca reports no exploitation in the wild at the time of writing.
How a single byte becomes a problem
The bug involves how Ruby changes letters from lower case to upper case. It affects several older single-byte text encodings. These include ISO-8859-1 and Windows-1252.
In those encodings, the German letter ß (byte 0xDF) becomes two letters, "SS", in upper case. One character turns into two. Ruby set aside room for only one byte in the output.
A crafted string packed with such characters pushes Ruby one byte beyond the memory it reserved. The fix makes Ruby guarantee two bytes of space for each conversion.
One byte sounds trivial. Orca says that this kind of memory damage on the heap can be turned into code execution. Per the researchers, the bug can be triggered through upcase, swapcase, downcase(:fold) and casecmp?. UTF-8 text follows another route in the code, so it is not hit.
The researchers also say the flaw can be reached with no login in default Ruby on Rails apps and classic-style Sinatra apps. That is their claim, relayed by Orca. WebPulse has not tested it.
Why updating gems will not help
Orca stresses that the fix is in the Ruby interpreter, not in a gem. Running bundle update leaves the flaw in place.
Ruby also travels inside other products and container images. The researchers name GitLab, GitHub Enterprise Server, Mastodon, Discourse, OpenProject and Chatwoot. They say the latest versions of each were affected when the flaw was disclosed. These products need updates from their own vendors.
Linux distributions add another wrinkle. Orca says a distribution may repair Ruby in a package but keep the old version number. Checking the version string alone could mislead. The distribution's own advisory is the better guide.
Ruby 3.2 and older are past end of life, so they get no fix. Teams on those versions must move to a supported branch.
The same release repairs six other memory-safety flaws. They sit in Ruby's regular expression engine and in string case conversion. The Ruby team says it has seen working remote code execution exploits for five of the seven flaws in total. Upgrading to a fixed version covers all seven. Orca reports that no official workaround exists.
Questions to put to your team
Can we list every Ruby runtime we run? Count operating system packages, version managers, tarball installs, container images and Ruby bundled inside self-hosted products.
Which internet-facing Rails or Sinatra apps handle untrusted input? Orca advises fixing those first.
Which vendors ship Ruby inside their products? When will they release builds on the fixed Ruby versions? Do any of our applications run Ruby 3.2 or older?
Orca sells tools that find vulnerable Ruby versions, so its sense of urgency also serves its business. The Ruby team's own rating and upgrade advice stand apart from that. A vulnerability inventory that stops at the gem list stops one layer too soon.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Orca Security.





