Disclosure: this page contains affiliate links. East Bay Cyber may earn a commission if you buy through them, at no extra cost to you. That never changes how we rank products. Editorial policy.
Ruby patches Ruby2Shell flaw among seven memory-safety issues
TL;DR - Ruby released 4.0.10, 3.4.13 and 3.3.14 for seven vulnerabilities. - Ruby2Shell is identified by CVE-2026-132825 in research and news reporting, and by GHSA-34m4-m9fh-gqp5 in Ruby’s advisory. - Ruby says proof-of-concept exploits demonstrate remote code execution for some vulnerabilities. - Affected Ruby versions include 3.3.13 and earlier, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9. - Veria Labs plans to publish a Ruby2Shell proof of concept on 25 November 2026, or later if major vendors have not shipped a fix.
What happened#
Ruby announced seven vulnerabilities in its regular expression engine and string case-conversion functionality. The Ruby project says it is aware of proof-of-concept exploits that demonstrate remote code execution for some of the issues. It released Ruby 4.0.10, 3.4.13 and 3.3.14, and strongly recommends upgrading. Ruby’s security advisory says CVE identifiers had been requested but had not been assigned when the notice was published, so it identifies the issues with GitHub Security Advisory identifiers.
Research and news reporting identify the string case-conversion issue as Ruby2Shell, CVE-2026-132825. Previdian describes it as a one-byte heap buffer overflow involving legacy single-byte encodings, including ISO-8859-1 and Windows-1252. Veria Labs says the affected code can write two bytes after checking space for one. UTF-8 strings follow a different code path and are not affected by this particular flaw, according to Veria Labs. Previdian’s analysis attributes the issue to GHSA-34m4-m9fh-gqp5.
Ruby’s advisory also covers double-free, integer-overflow, heap-buffer-overflow and out-of-bounds-read issues in regular expression processing and string case conversion. SecurityWeek reports that proof-of-concept code demonstrating RCE exists for five of the seven vulnerabilities. SecurityWeek reports that the other issues include a double free, two integer overflows, a heap-based buffer overflow and out-of-bounds reads.
Are you affected#
Ruby lists these affected versions:
- Ruby 3.3.13 and earlier
- Ruby 3.4.0 through 3.4.12
- Ruby 4.0.0 through 4.0.9
Ruby 3.2 and earlier have reached end of life and will not receive these fixes, according to the Ruby project. Veria Labs lists releases dating back to Ruby 2.4.0 as affected by Ruby2Shell, with Ruby 3.2 and older marked end of life. Veria Labs’ affected-version table lists fixed versions as Ruby 3.3.14, 3.4.13 and 4.0.10.
Veria Labs says Ruby2Shell is reachable in Rails and classic-style Sinatra applications using their default configurations. It says other frameworks and plain Rack applications are not exposed by default, although application code that upcases strings received in a legacy encoding may also be vulnerable.
Applications may use a Ruby runtime bundled by a product rather than the system Ruby installation. Veria Labs lists GitHub Enterprise Server 3.22.5 and earlier as vulnerable with no fixed release listed. It lists fixed updates for Chatwoot, GitLab, Mastodon, OpenProject and the Discourse base image. Deployment-specific verification remains necessary.
What is confirmed and what is reported#
| Claim | Source | Status |
|---|---|---|
| Ruby released 4.0.10, 3.4.13 and 3.3.14 for seven vulnerabilities. | Ruby | Confirmed |
| A heap buffer overflow in string case conversion may allow RCE in some scenarios. | Ruby | Confirmed |
| CVE-2026-132825 is associated with Ruby2Shell and GHSA-34m4-m9fh-gqp5. | Previdian | Reported |
| PoCs demonstrate RCE for some of the seven vulnerabilities. | Ruby | Confirmed |
| Ruby2Shell is reachable without authentication in default Rails and classic-style Sinatra configurations. | Veria Labs | Reported |
| No confirmed in-the-wild exploitation was identified in the public material reviewed by 19 November 2026. | Previdian | Reported |
| Veria Labs plans to publish a Ruby2Shell PoC on 25 November 2026, or later if major vendors have not shipped a fix. | Veria Labs | Reported |
| GitHub Enterprise Server 3.22.5 and earlier are listed as vulnerable, with no fixed release listed. | Veria Labs | Reported |
What defenders should do now#
- Identify Ruby installations across application servers, containers, background workers and bundled runtimes.
- Upgrade supported Ruby installations to Ruby 4.0.10, 3.4.13 or 3.3.14, following Ruby’s recommendation.
- Check self-hosted products that bundle Ruby and install the appropriate vendor update. Updating a system Ruby installation alone may not update a bundled runtime.
- Rebuild containers and restart affected processes, then verify that the updated Ruby runtime is running.
- Review Rails and classic-style Sinatra applications for exposure, especially where untrusted strings using legacy encodings are processed or case-converted.
- Check the product-specific status of GitHub Enterprise Server, Chatwoot, GitLab, Mastodon, OpenProject and Discourse deployments against the fixed versions listed by Veria Labs.
- Where patching is delayed, restrict public access to affected services, particularly internet-facing applications using affected Ruby versions.
- Track further technical details and the planned PoC release, while distinguishing proof-of-concept availability from confirmed exploitation against real-world systems.
This advisory is informational and is updated as vendors publish details. Confirm versions and actions against the vendor’s own guidance for your environment.
Sources
- Primary notice: ruby-lang.org
- Research: blog.previdian.com
- Research: verialabs.com
- Report: securityweek.com