AI Weekly Malaysia

Back to items Summaries

Ruby2ßhell: Pre-authentication RCE on stock Rails

ID
48449
Status
summarized
Published
19 Nov 2026, 1:09 PM
Fetched
20 Nov 2026, 4:26 AM
Provider
Hacker News
Category
dev-community
Original URL
https://verialabs.com/ruby2shell/
Source URL
https://hnrss.org/best

Summary

Score
9.0
Created
20 Nov 2026, 4:27 AM
Tags
Audience
developersvibe_coderssaas_founders

What happened

Veria Labs disclosed ruby2ßhell (GHSA-34m4-m9fh-gqp5), a one-byte heap overflow in Ruby's single-byte encoding case conversion that reaches pre-authentication remote code execution in default-config Rails and classic Sinatra. Upcasing ß writes two bytes ('SS') into a buffer sized input+20 with only a one-byte bounds check, so 21 ß characters in a legacy encoding overflow by one byte; the loop has existed since Ruby 2.4.0 and is reached via upcase, swapcase, downcase(:fold) and casecmp?, while UTF-8 strings take a different path and are unaffected. Fixed in Ruby 3.3.14, 3.4.13 and 4.0.10, but GitLab 19.6.0 (bundles 3.3.13), GitHub Enterprise Server 3.22.5 (bundles 4.0.9) and Chatwoot 4.20.0 (bundles 3.4.4) still ship affected Rubies; Mastodon, OpenProject and Discourse base images are already on 4.0.10. No proof of concept yet — it is being withheld for a week to allow upgrades.

Why it matters

Run `ruby -v` today: anything in 3.3.0–3.3.13, 3.4.0–3.4.12 or 4.0.0–4.0.9 needs upgrading to 3.3.14 / 3.4.13 / 4.0.10 before the PoC lands roughly a week from the 19 Nov 2026 disclosure. If you self-host GitLab 19.6.0 or GitHub Enterprise Server 3.22.5, patching your app's Gemfile is not enough — the bundled interpreter is still vulnerable and you are waiting on the vendor. Ruby 3.2 and everything back to 2.4.0 is EOL with no fix listed, so any service still on 3.2 needs a series upgrade, not a patch.

Discussion angle

How do you inventory the Ruby version bundled inside every self-hosted tool you run (GitLab, GHES, Chatwoot) rather than just the Ruby in your own repo — and who in the room is still on EOL 3.2 with no upstream fix?

Top