TL;DR
On November 20, 2026, GitLab shipped urgent patches to fix the GitLab Ruby2Shell vulnerability, tracked as CVE-2026-132825. This critical Ruby string bug can cause a heap overflow and remote code execution. Self-hosted admins must upgrade to GitLab 19.6.1, 19.5.8, or 19.4.10 right away.
- CVE: CVE-2026-132825
- CVSS: 7.4 (High · CVSSv3)
- Product: ruby-lang Ruby
- Affected: < 3.3.14, 3.4.0, 4.0.0
- Impact: CWE-122
- Status: No confirmed exploitation yet
- Patched in: 3.3.14, 3.4.13, 4.0.10
- EPSS: 0.2% (30-day)
- Action: Update to 3.3.14, 3.4.13, 4.0.10 now
Why It Matters
GitLab states that over 70 million users and half of the Fortune 100 rely on its platform. Because teams store private code and CI jobs on self-hosted nodes, an RCE bug creates high risk. While Ruby maintainers note that proof-of-concept chains exist, watchTowr confirms no live attacks in the wild so far.
How the Attack Works
One-Byte Heap Overflow in Ruby
The GitLab Ruby2Shell vulnerability (GHSA-34m4-m9fh-gqp5) sits inside the bundled Ruby engine rather than GitLab’s own code. Specifically, Veria Labs staff found an off-by-one heap write in Ruby’s case_map code for formats like ISO-8859-1 and Windows-1252. In the official GitLab 19.6.1 patch release advisory, GitLab warns: “In GitLab, under certain conditions, changing the case of a crafted string can result in an out-of-bounds heap write. The Ruby security team has stated that this flaw may allow remote code execution in some scenarios.”
Furthermore, the Ruby team rates this bug Critical, while MITRE assigns it a 7.4 High CVSS score.
Affected Versions
This GitLab Ruby2Shell vulnerability hits all GitLab CE and EE builds before 19.4.10, 19.5 before 19.5.8, and 19.6 before 19.6.1. However, GitLab.com and GitLab Dedicated already run patched code.
Patch and Mitigation Steps
GitLab states: “These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately.” Official Linux packages and containers bundle Ruby 3.3.14 or 3.4.13. Finally, teams running self-built nodes must rebuild Ruby to 3.3.14 or 3.4.13 by hand.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!