Ruby (GitLab, GitHub Enterprise Server, Chatwoot) · CVE-2026-132825
Ruby2Shell
Patch now if…Rails or classic Sinatra on old Ruby. No public exploit.
A one-byte memory bug in how Ruby changes the case of text in older Western encodings (like ISO-8859-1) may let an attacker with no login run code on the server. The researchers who named it say default Rails and classic-style Sinatra apps reach it. The fix is a Ruby upgrade, which also fixes six related regex and string bugs.
How scary is it?
Are you affected? only if all are true
1Ruby older than the fixcommand
Affected: 3.3.13 and earlier, 3.4.0–3.4.12 and 4.0.0–4.0.9. Ruby 3.2 and older are end of life and won't get a fix. Check the Ruby your app actually runs (its container image or .ruby-version), not just the system one. Distros may patch without changing the version; on 20 Nov Ubuntu (priority Medium) and Debian were still evaluating.1,2,6,8,9
ruby -v2Web input gets case-changedcommand
Veria Labs says default Rails and classic-style Sinatra apps reach the bug with no login, but hasn't said through which code path. Other frameworks and plain Rack aren't exposed by default, unless your code calls upcase, swapcase, downcase(:fold) or casecmp? on ISO-8859 or Windows-125x text; UTF-8 isn't affected. Sources disagree on reach: Ruby rates it Critical, the CVE record scores it 7.4 (local), and Sekurak thinks a crash is likelier than code execution. Run the check in your app's folder.2,3,4,6,7
bundle list | grep -E '\* (rails|sinatra) \('What to do
1Upgrade Ruby
To 3.3.14, 3.4.13 or 4.0.10. Then restart app servers and rebuild container images. Updating Rails or other gems doesn't help: the fix is in Ruby itself.1,5,6
Latest safe versions checked 20 Nov
2On Ruby 3.2 or older? Move up
These are end of life and won't be fixed. Move to a supported series.1
3Update self-hosted appscommand
Some bundle their own Ruby, which a system upgrade doesn't touch. On 19 Nov, Veria listed GitLab 19.6.0, GitHub Enterprise Server 3.22.5 and Chatwoot 4.20.0 as still affected, and Mastodon 4.7.6, OpenProject 17.9.8 and the Discourse base image 2.0.20261119-0203 as fixed. Aikido's list, made earlier, shows older versions of the last three as affected. For GitLab, check its bundled Ruby with the command below.4,5,6
/opt/gitlab/embedded/bin/ruby -v4Can't upgrade yet?
Ruby gives no workaround. For self-hosted apps, Aikido suggests keeping them reachable only over VPN or an IP allowlist until the vendor ships a fix.5
5Patch before the exploit is outPending · expected 25 Nov
Veria Labs plans to publish its proof of concept on 25 Nov 2026, or later if major vendors haven't shipped a fix by then.4
This page shows you how to check. It can't tell you you're safe.
Sources (10) and changelog
- Ruby: security advisory, versions, PoCs known 18 Nov
- GitHub: GHSA-34m4-m9fh-gqp5, rated Critical 19 Nov
- CVE record: CVE-2026-132825, CVSS 7.4 local 19 Nov
- Veria Labs: write-up, frameworks, bundled apps 19 Nov
- Aikido: no attacks, no workaround, VPN advice 19 Nov
- Equixly: gem updates don't help, Rails path unknown 19 Nov
- Sekurak: doubts reliable code execution 19 Nov
- Ubuntu: CVE tracker
- Debian: security tracker
- CISA KEV catalog: not listed
- Rechecked: no fixed GitLab, GitHub Enterprise Server or Chatwoot release yet; Veria's 25 Nov plan unchanged.
- Veria moved its exploit release to 25 Nov (later if vendors haven't shipped fixes). Safe versions added.
- Published.