What is new
Our earlier coverage of the Ruby 4.0.10, 3.4.13 and 3.3.14 releases noted that CVE IDs were pending. One of the critical bugs, the one-byte heap overflow in string case conversion, now has an ID: CVE-2026-132825, scored CVSS 7.4. Researchers are calling it Ruby2Shell. SecurityWeek reports the new details below.
How the bug works
In some single-byte encodings, including ISO-8859-1 and Windows-1252, Ruby can write one byte past the end of its output buffer when it changes a string's case. Upper-casing the German letter "ß" produces "SS": Ruby reserves space for one byte but writes two. The extra byte can corrupt adjacent heap memory, which may lead to remote code execution in some scenarios.
Who is exposed
- Veria Labs says default configurations of Rails and classic-style Sinatra, and potentially other frameworks, are exposed to unauthenticated attackers.
- GitHub Enterprise Server is also affected.
- WatchTowr says any Ruby application that changes the case of external text in a single-byte encoding is affected.
Exploitation outlook
Veria Labs plans to release a proof-of-concept only after major vendors have shipped patches, so no public PoC for this bug has been described. WatchTowr's Yordan Ganchev says reliable exploitation would be difficult. It needs a precise memory layout, specific allocator and runtime conditions, and a way past ASLR. He expects malformed requests to mostly cause denial of service. No in-the-wild exploitation has been reported.
Patch status
| Item | Detail |
|---|---|
| CVE | CVE-2026-132825 |
| CVSS | 7.4 |
| Fixed in | Ruby 4.0.10, 3.4.13, 3.3.14 |
| Already patched | Chatwoot, GitLab, Mastodon, OpenProject, Discourse base image |
The same release fixes six other flaws, including a regex-engine out-of-bounds read. Four of them have RCE PoCs, and CVE IDs for those were requested but not yet assigned.
Recommended actions
- Upgrade the Ruby interpreter to 4.0.10, 3.4.13 or 3.3.14, then restart or rebuild application servers, workers and container images.
- Updating gems or Rails does not replace a vulnerable interpreter.
- Rebuild any base images your apps inherit from, and check vendor-supplied Ruby apps such as self-hosted GitLab, Mastodon and Discourse.
- Move Ruby 3.2 and earlier to a supported line, as they get no fix.
- Expect a PoC soon after vendor patches land, so patch internet-facing apps first.