Another week, another "2Shell." This one's in Ruby itself, and the detail that matters most is a boring one: it lives in the interpreter, not in Rails. bundle update does nothing for you here.
What Happened
On November 18, the Ruby team shipped Ruby 4.0.10, 3.4.13 and 3.3.14 with fixes for seven memory safety bugs in the regex engine and in string case conversion (think upcase and downcase). The official advisory rates three critical, three high and one moderate.
From the advisory:
- The headline bug (GHSA-34m4-m9fh-gqp5) is a one-byte heap overflow when changing the case of a crafted string, which "may allow remote code execution." Some outlets list it as CVE-2026-132825; Ruby's own advisory says CVEs were requested but not yet assigned, so it uses GHSA IDs for now.
- The regex bugs mostly matter if your app compiles patterns built from user input (a double free, integer overflows, out-of-bounds reads).
- PoCs exist. The maintainers say they're aware of PoCs that prove some of the bugs can lead to code execution. They do not report exploitation in the wild.
- Affected: Ruby 4.0.0 to 4.0.9, 3.4.0 to 3.4.12, and 3.3.13 and earlier. Ruby 3.2 and older are end of life and won't get fixes.
The "Default Rails, Pre-Auth" Part
The name and the urgency come from third-party research, not the Ruby advisory. Per The Hacker News, Veria Labs says the case-conversion bug is reachable unauthenticated over the network in default Rails and classic-style Sinatra apps, and a separate analysis says Rack changes the case of a request field while processing a crafted form submission, before your app code ever runs. Veria says it'll publish a PoC about a week after disclosure.
The Ruby advisory itself doesn't say anything about Rails or Rack reachability, so I'm treating that as a credible researcher claim, not a confirmed fact. It doesn't really change the advice. If there's even a decent chance a stock web app hits the bug on a form post, you patch like it's real.
Why This One Is Sneaky
Most teams patch Ruby apps by bumping gems. Dependabot opens a PR, CI runs, done. This fix doesn't come through that path. It comes through:
- the base image in your Dockerfile (
ruby:3.4-slimpinned to an old digest, anyone?), - the OS package on long-lived VMs,
- the
.ruby-versionfile nobody has touched since 2023, - the Sidekiq workers and cron boxes that never get rebuilt because "they're just background jobs."
And Ruby 3.2 and older are simply not getting fixed. If you're there, this is the push to move.
I work at Zscaler, and I'll admit nothing about this is a network problem. Keeping your apps off the open internet where you can (private access instead of exposed admin and internal tools) shrinks how many of them are reachable on day one. But the public app is public, and it needs the patch.
What To Do
- Update Ruby to 4.0.10, 3.4.13 or 3.3.14 everywhere it runs: app servers, workers, CI runners, container base images. Then restart or rebuild. An updated package with an old process still running is still vulnerable.
- Find your 3.2-and-older stragglers and plan the upgrade. There's no fix coming for them.
- Inventory by image, not by repo. Scan your registries for Ruby versions. The repo says what you meant to ship; the image says what you shipped.
- Review code that builds regexes from user input. It was a bad idea before this week and it's a worse one now.
- Watch for the PoC. Veria's timeline puts it around next week. Expect scanning shortly after.
Bottom Line
Seven interpreter bugs, PoCs already exist, a credible claim that default Rails apps are reachable pre-auth, and a fix that doesn't arrive through your normal dependency updates. Patch the runtime, rebuild the images, and don't forget the workers.
Sources: Ruby security advisory, Nov 18, Ruby security page, The Hacker News