Ruby2Shell: Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution, But is it an Actual Risk?
Our summary
The Ruby core team patched seven security flaws on November 18, 2026, releasing versions 4.0.10, 3.4.13 and 3.3.14. The headline bug, CVE-2026-132825 (rated 7.4, High), is a one-byte heap overflow in Ruby's string case-conversion routines affecting legacy single-byte encodings like ISO-8859-x and Windows-125x; triggering it requires feeding a specially crafted string containing the character ß into methods such as upcase, swapcase, capitalize, casecmp? or downcase(:fold). Six additional flaws in the regex engine are still awaiting CVE numbers and scores. Because the issue sits in Ruby itself, it potentially touches any app built on it, including Rails projects, GitLab, GitHub Enterprise Server, Mastodon and Discourse, though UTF-8-only applications are unaffected and exploitation has not been observed in the wild, with researchers noting that weaponizing it reliably into remote code execution would require substantial additional work.
Below is the opening; the full story is at OX Security.
From OX Security
A one-byte heap overflow in Ruby’s string case conversion, plus six related flaws in the regex engine, could let attackers crash or take over Ruby applications. Administrators are urged to upgrade to Ruby 4.0.10, 3.4.13 or 3.3.14.
On November 18, 2026, the Ruby core team disclosed seven vulnerabilities in Ruby’s regular expression engine and string case conversion, and released Ruby 4.0.10, 3.4.13 and 3.3.14 to fix them. The first to get a CVE is CVE-2026-132825, a one-byte heap overflow in string case conversion. Ruby’s maintainers say proofs of concept show some of these flaws can lead to remote code execution, and even without code execution, a crafted request can crash the Ruby process. No exploitation in the wild has been reported so far.…
Worried this affects your company?
Discuss a security assessment of your internet-facing systems. Scope agreed before testing.