Ruby vulnerabilities in 2026: Ruby2Shell (not a breach of the Ruby project)
Ruby is the open-source language behind Rails, Sinatra and self-hosted products such as GitLab and Mastodon. A flaw in the Ruby interpreter reaches every application that runs on it, and updating a gem does not fix it. This page tracks Ruby2Shell and keeps the Ruby project's advisory apart from what researchers say about exposure.
Short answer
Was Ruby hacked?
No, Ruby2Shell is not a breach of ruby-lang.org or the Ruby project: nothing reported shows an intrusion at Ruby. It is a vulnerability in the Ruby interpreter. On 18 November 2026 Ruby released 4.0.10, 3.4.13 and 3.3.14 to fix seven flaws in its regular expression engine and string case conversion, including GHSA-34m4-m9fh-gqp5 (CVE-2026-132825), a one-byte heap buffer overflow when changing the case of strings in certain single-byte encodings. Ruby says it may allow remote code execution in some scenarios.
Veria Labs, which named it Ruby2Shell on 19 November, says Rails and classic-style Sinatra apps reach it by default without authentication. No exploitation is reported and it is not in CISA KEV; Veria plans to publish a proof of concept on 25 November 2026. Ruby 3.2 and earlier are end of life and will not be fixed.
Timeline at a glance
18 Nov 2026Ruby advisory on seven Regexp and case-conversion flaws; Ruby 4.0.10, 3.4.13 and 3.3.14 released. (ruby-lang.org)Not a breach
19 Nov 2026CVE-2026-132825 published (CVSS 3.1 7.4 per MITRE; GitHub advisory rates it Critical); CISA enrichment: exploitation none. (CVE.org)Not a breach
19 Nov 2026Veria Labs names it Ruby2Shell and says Rails and classic Sinatra apps are reachable by default; PoC planned for 25 Nov. (Veria Labs)Reported
20 Nov 2026GitLab ships 19.6.1, 19.5.8 and 19.4.10 with an updated bundled Ruby. (GitLab)Not a breach
Last updated 20 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.
Ruby incident timeline, in detail
Confirmed = acknowledged by Ruby, a regulator filing or a court. Reported = credible reporting Ruby has not fully confirmed. Unverified claim = an attacker or leak-site claim.
Nov 2026Not a breachProduct vulnerability
Ruby2Shell (CVE-2026-132825): one-byte heap overflow in string case conversion
What happened. Ruby's advisory GHSA-34m4-m9fh-gqp5: changing the case of a crafted string in certain single-byte encodings, such as ISO-8859-1 and Windows-1252, can write one byte past a heap buffer. Affected: Ruby 3.3.13 and earlier, 3.4.0 through 3.4.12 and 4.0.0 through 4.0.9; fixed in 3.3.14, 3.4.13 and 4.0.10. Ruby 3.2 and earlier will not receive the fix. Ruby credits Stephan Lipp (Ada Logics) and Anthropic; Veria Labs says it found it independently and demonstrated remote code execution on stock Rails.
Impact. Possible remote code execution "in some scenarios" (Ruby). Veria says Rails and classic-style Sinatra reach it by default without authentication, plain Rack and other frameworks do not, and UTF-8 strings are unaffected. No workaround from Ruby. Products that bundle Ruby need vendor builds: GitLab and Mastodon have shipped them. CISA enrichment on 19 November: exploitation none; not in KEV.
Severity: the GitHub advisory rates it Critical with no score; the CVE record (CNA MITRE) gives CVSS 3.1 7.4 with a local attack vector; Red Hat gives a preliminary 9.8 with a network vector; Ubuntu gives Medium priority.
Exposure: Veria says Rails and classic Sinatra reach the flaw by default; Red Hat notes exploitation depends on non-UTF-8 handling and that most default deployments use UTF-8. We found no statement from the Rails or Sinatra projects.
Versions: Ruby lists the 3.3 line as "3.3.13 and earlier"; Veria lists 3.3.0 to 3.3.13 and puts older branches back to 2.4.0 separately. Ruby does not state when the bug was introduced. We follow ruby-lang.org.
Credits: Ruby credits Stephan Lipp (Ada Logics) and Anthropic; Veria says it found the bug independently and also lists Moritz Sanft with OpenAI.
The pattern across the record
Runtime flaws are fixed only in the runtime
Like PHP2Shell and phpAfterShell, Ruby2Shell sits in the language runtime, so every app inherits it and no gem update fixes it. Container images and bundled products keep the old interpreter until rebuilt.
Vulnerabilities are not breaches
Nothing reported shows an intrusion at the Ruby project. The exposure is to every organisation running an unpatched Ruby.
What it means for Ruby customers — and what to do
If you run Rails, Sinatra or a product that ships its own Ruby, the question is which Ruby each process runs, not whether Ruby was breached.
1.Upgrade Ruby everywhere
Move to 4.0.10, 3.4.13 or 3.3.14, restart every Ruby process and rebuild container images before the planned 25 November proof of concept.
Products that bundle Ruby need the vendor's release: GitLab 19.6.1, 19.5.8 or 19.4.10 and Mastodon 4.7.6 have shipped. Restrict access to anything still unpatched.
Independent analysis for security-leadership education; not affiliated with or endorsed by Ruby. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.