On this page
Ruby2Shell, stylised "ruby2ßhell", is a critical one-byte heap overflow in Ruby's string case conversion that researchers say can be reached without logging in on default Rails and classic-style Sinatra apps. Ruby published its advisory on 18 November 2026, and the fix is to upgrade Ruby to 3.3.14, 3.4.13 or 4.0.10.
What is the Ruby2Shell vulnerability?
Ruby2Shell is a critical one-byte heap overflow in how Ruby changes the case of strings in some legacy single-byte encodings. Veria Labs says default Rails and classic-style Sinatra apps can reach it without authentication. Ruby 3.3.14, 3.4.13 and 4.0.10 fix it, and Ruby lists no workaround.
The Ruby core team announced fixes for seven vulnerabilities in its regular expression engine and string case conversion on 18 November 2026. Ruby2Shell is the name given to one of them: GHSA-34m4-m9fh-gqp5. The GitHub advisory, published on 19 November 2026, rates it critical and describes an off-by-one error (CWE-193). Changing the case of a string in some single-byte encodings, such as ISO-8859-1 and Windows-1252, can write one byte past the end of the output buffer.
The advisory credits Stephan Lipp of Ada Logics and Anthropic with the report. It says the flaw may allow remote code execution and that proof-of-concept exploits exist for some scenarios. The name and the technical write-up come from Veria Labs.
Why does it matter for Rails?
Veria Labs says Rails and classic-style Sinatra applications reach the vulnerable code in their default configurations, so no account is needed. It says plain Rack and other frameworks are not exposed by default, and that application code which changes the case of untrusted strings in a legacy encoding may also be vulnerable. UTF-8 strings are not affected, according to Equixly's analysis.
Because the bug sits in the Ruby interpreter, updating Rails or other gems does not remove it. Equixly adds that every Ruby process must be restarted, and that a Puma phased restart does not pick up a new Ruby.
Which Ruby versions are affected and fixed?
| Ruby branch | Affected | Fixed in |
|---|---|---|
| 4.0 | 4.0.0 to 4.0.9 | 4.0.10 |
| 3.4 | 3.4.0 to 3.4.12 | 3.4.13 |
| 3.3 | 3.3.13 and earlier | 3.3.14 |
| 3.2 and older | Affected back to 2.4.0, according to Veria Labs | No fix (end of life) |
Ruby's advisory lists no workaround and says only that applications should upgrade. Ruby 3.2 and earlier are end of life and will not be patched, so those applications need to move to a supported branch.
What is the CVE ID?
Sources disagree. The Ruby advisory and the GitHub entry say a CVE has been requested and is pending. Aikido and Orca Security both report the identifier CVE-2026-132825. We could not confirm that number on the official Ruby pages, so treat it as a vendor-reported ID until Ruby or a CVE database lists it. The GHSA identifier is the one that is certain.
Which self-hosted products bundle Ruby?
Veria Labs lists GitLab 19.6.0 (bundling Ruby 3.3.13), GitHub Enterprise Server 3.22.5 (bundling 4.0.9) and Chatwoot 4.20.0 (bundling 3.4.4) as affected. It says Mastodon 4.7.6, OpenProject 17.9.8 and the Discourse base image 2.0.20261119-0203 are fixed. Check each vendor's current release notes, because this picture is changing quickly.
Is it being exploited?
Aikido says no attacks had been reported as of 19 November 2026. Ruby says it knows of proofs of concept, and Veria Labs says it plans to publish its own about a week after disclosure to give people time to upgrade. That gives defenders a short window.
What should administrators do?
- Check the Ruby version each running process actually uses, including bundled runtimes and container base images.
- Upgrade to 3.3.14, 3.4.13 or 4.0.10, then restart every Ruby process and rebuild container images.
- For self-hosted products, install the vendor's fixed release. Until then, Equixly suggests restricting access, for example behind a VPN or IP allowlist.
- Move Ruby 3.2 and older applications to a supported branch or take them off the internet.
Analysis: a platform-level fix again
This is our own reading, not a claim from the advisories. Our recent coverage of the NGINX HTTP/2 vulnerability, the Java4Shell OpenJDK flaw and the Apache HTTP Server flaw shows a similar pattern: the fix lives in the platform, not the application, so teams must find where the runtime is bundled. The practical gap here is inventory. Many teams know their Rails version but not the Ruby inside each container or vendor appliance.
Sources
FAQ
Frequently asked questions
No. The flaw is in Ruby itself, so you need a fixed Ruby release (3.3.14, 3.4.13 or 4.0.10) and a restart of every Ruby process.
No. [Akamai](https://www.akamai.com/blog/security-research/rails-active-storage-rce-cve-2026-66066) describes KindaRails2Shell as a different flaw, CVE-2026-66066, in Rails Active Storage. Ruby2Shell is a bug in the Ruby interpreter.
Ruby's advisory lists none. Upgrading is the fix. Restricting access to self-hosted tools is only a stopgap.
No. They are end of life and will not be patched, though Veria Labs says they are affected back to Ruby 2.4.0.
Spotted an error? Tell us. Read how we report and correct stories in our editorial policy.
Written by
Mainstream Tech
Newsroom
News and analysis on technology, AI, business, politics and international affairs, from our newsroom in London.
More from Mainstream




