Ruby2Shell (CVE-2026-132825): Ruby Is Fixed, but GitLab, GitHub Enterprise and Chatwoot Are Listed Without a Patch
Security / news
Ruby2Shell (CVE-2026-132825): Ruby Is Fixed, but GitLab, GitHub Enterprise and Chatwoot Are Listed Without a Patch
A one-byte heap overflow in Ruby's case conversion carries a 7.4 local score, while the researchers say stock Rails is remotely reachable and will publish a proof of concept Nov. 25.
An attacker who can feed text in a legacy single-byte encoding to Ruby's case-conversion methods can write one byte past the end of a heap buffer, and a write-up published Nov. 19 says that is reachable without authentication in a default Rails or classic-style Sinatra app. The bug is CVE-2026-132825. Ruby fixed it in 4.0.10, 3.4.13 and 3.3.14, but the same write-up lists GitLab, GitHub Enterprise Server and Chatwoot as still vulnerable.
A proof of concept for remote code execution on stock Rails is planned for Nov. 25, "or later if major vendors have not shipped a fix by then", according to the write-up hosted at verialabs.com, which is titled Ruby2Shell.
How CVE-2026-132825 works
The German sharp s (ß, byte 0xDF) has no capital form in most of Ruby's single-byte encodings. Upcasing it writes two bytes, "SS", but the loop checks for room for only one. The output buffer is the input length plus 20 bytes, so a string holding 21 of the character overflows it by exactly one byte.
The commit that fixes it, d582f8f in the ruby/ruby repository, says the case_map functions of ISO-8859-x and Windows-125x "mapped the sharp s (0xDF) to two bytes but checked for only one byte of room". The write-up says the code has been present since Ruby 2.4.0. UTF-8 strings take a different path and are not affected.
The methods that reach it are upcase, swapcase, downcase(:fold) and casecmp?. The overwritten byte is "S" (0x53) on upcase or "s" (0x73) on case folding, and the attacker sets the buffer size through input length.
Who is exposed, as of Nov. 19
The write-up's table lists the following as of its 22:29 UTC update on Nov. 19. These are the researchers' statuses, not vendor advisories, and the table should be read that way.
| Software | Affected through | Status listed |
|---|---|---|
| GitLab | 19.6.0 | No fix |
| GitHub Enterprise Server | 3.22.5 | No fix |
| Chatwoot | 4.20.0 | No fix |
| Mastodon | 4.7.5 | Fixed in 4.7.6, 4.6.12, 4.5.22, 4.4.29 |
| OpenProject | 17.9.7 | Fixed in 17.9.8, 17.8.3 |
| Discourse base image | Before 2.0.20261119-0203 | Fixed in 2.0.20261119-0203 |
Ruby itself is affected in 4.0.0 through 4.0.9, 3.4.0 through 3.4.12 and 3.3.0 through 3.3.13. Ruby 3.2 and older, back to 2.4.0, are affected and end of life, so no upstream fix is coming for them.
The score understates the claimed reach
The CVE record, assigned by MITRE on Nov. 19, rates the flaw 7.4 with the vector AV:L/AC:H/PR:N/UI:N. That is a local attack vector with high complexity. The write-up claims the opposite for web frameworks: Rails and classic-style Sinatra are exposed "in default configuration", while plain Rack and other frameworks are not exposed by default.
Both can be true. The CVE vector describes the library call, and the network reach depends on whether an application passes request data in a legacy encoding to those methods. Which of them holds for a given deployment is something only an inventory answers. The remote-code-execution claim is unproven in public until the proof of concept appears.
The fix commit carries a Co-Authored-By trailer naming "Claude Mythos 5.1" and credits Stephan Lipp as reporter. The site's earlier report on the Ruby 4.0.10 release covers the other string and regex advisories that shipped in the same releases.
Timeline
- Oct. 28, 2026: Yusuke Endoh authors the fix commit.
- Nov. 18, 2026: the commit is committed to ruby/ruby at 22:18 UTC.
- Nov. 19, 2026: MITRE assigns CVE-2026-132825 at 06:34 UTC; the write-up is updated at 22:29 UTC.
- Nov. 25, 2026: planned release of the proof of concept.
What to do before Nov. 25
Upgrade Ruby to 4.0.10, 3.4.13 or 3.3.14. For GitLab, GitHub Enterprise Server and Chatwoot, no fixed build is listed, so the choice is to watch each vendor's advisory page. Teams that run an unpatched Rails app can search for upcase, swapcase and casecmp? calls on strings that are not UTF-8. For comparison with a flaw that already has a fix and a version number to chase, see nginx2root; here the window closes when the proof of concept goes public.
Sources
More in Security
- 01NPCI Wants Overlay Permissions Restricted on Sideloaded Apps; Google's 2024 India Block List Omits ThemThe reported ask covers accessibility, device admin and display-over-apps. The pilot Google announced on Oct. 3, 2024 named four other permissions.
- 02CVE-2026-99312: A KVM Nested-AMD Bug Scores 8.8, With Fixes Listed for Three Kernel BranchesThe Linux CNA's scoring notes describe a freed page-table root that a guest can aim at; the commit message describes only a stale MMU context.
- 03CISA's Nov. 18 KEV Additions Include Apache Axis 1.x, Which Has No Fix, With a Nov. 21 DeadlineThree of four new entries carry a three-day federal deadline; LiteLLM's advisory names two different patched versions.
- 04NSANet Went Down Nov. 17 With 'Routine Maintenance' as the Only Cause on RecordOfficials from the White House to the Senate Intelligence Committee say they see no attack, but the NSA has not said which systems failed or for how long.