Regexp and String case conversion vulnerabilities
Archived — this story has rotated out of today’s deck. It is kept here in full.
The gist
Ruby's core team released 4.0.10, 3.4.13 and 3.3.14 to fix seven flaws in its regex engine and string case conversion.
The bugs sit in Ruby itself, so Rails apps and products like GitLab and Mastodon inherit them.
Background
Ruby is a programming language, and its core team is the group that maintains it and issues security fixes. The seven flaws sit in two parts of Ruby itself — string case conversion and the regular expression engine — so every application running an affected version carries them regardless of which libraries it uses. Ruby underpins Ruby on Rails and widely deployed products such as GitLab, GitHub Enterprise Server, Mastodon and Discourse, which is why the disclosure drew attention. One flaw, CVE-2026-132825, a one-byte heap overflow in string case conversion, was named Ruby2Shell by researchers at Veria Labs.
How it unfolded
- Nov 18, 2026The 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.
- Nov 18, 2026CVE-2026-132825, a one-byte heap overflow in string case conversion named Ruby2Shell by Veria Labs, became the first flaw to receive a CVE identifier; most others had none yet.
- Nov 19, 2026Security advisories were published and covered, listing affected ranges: Ruby 4.0.0 through 4.0.9 (fixed in 4.0.10), 3.4.0 through 3.4.12 (fixed in 3.4.13), and 3.3.13 and earlier (fixed in 3.3.14). Ruby 3.2 and earlier are end of life and not fixed.
- Nov 19, 2026Miggo reported it reproduced a denial-of-service condition on Rails and Sinatra applications.
Key terms
- regex engine
- Software component that interprets regular expressions, character patterns used to find, match, or replace text in strings.
- heap overflow
- A software bug where a program writes more data into a memory buffer than it can hold, overwriting nearby memory.
- CVE identifier
- A unique identifier in the CVE system for a publicly known information-security vulnerability.
Source: Wikipedia
Who’s saying what
- Official
- Ruby maintainers say they are aware of proofs of concept showing some flaws can be used to trigger remote code execution in some scenarios, and that one advisory's PoC shows attacker-controlled memory corruption with RCE possible but not demonstrated.
- Analysts
- The Brandefense Research Team notes every row uses Ruby's stated possibility rather than a claim about attacks in the wild, and that a PoC shows technical feasibility under tested conditions, not that the same result follows whenever an application receives user input.
- Caution
- Miggo Research reported no exploitation in the wild as of publication, while reproducing a denial-of-service condition on Rails and Sinatra applications.
Still unverified
Most of the flaws have no CVE identifiers yet; Ruby's seven-part announcement still lists GHSA identifiers while CVEs are pending. Remote code execution for GHSA-wpqw-5qxg-m68r is described as possible but was not shown by the PoC.