Skip to content
TrustList
Security advisories

GitLab critical patch 19.6.1, 19.5.8 and 19.4.10 fixes Ruby heap overflow

Editorial

By TrustList Editorial

GitLab released critical patch versions 19.6.1, 19.5.8 and 19.4.10 on 20 November 2026 to fix CVE-2026-132825, a heap overflow in Ruby string case conversion; self-compiled installs must rebuild Ruby 3.3.14 or 3.4.13.

About GitLab critical patch 19.6.1, 19.5.8 and 19.4.10 fixes Ruby heap overflow

GitLab critical patch 19.6.1, 19.5.8 and 19.4.10 fixes Ruby heap overflow

20 November 2026: GitLab released versions 19.6.1, 19.5.8 and 19.4.10 of GitLab Community Edition and Enterprise Edition as a critical patch release, outside its usual schedule of the second and fourth Wednesdays. It asks every self-managed installation to upgrade to one of these versions immediately. GitLab.com and GitLab Dedicated already run patched versions, and their customers do not need to act.

Not yet independently verified. Versions and ratings come from GitLab's own patch release page of 20 November 2026, read the same day. GitLab gives the Ruby security team's Critical rating and MITRE's High rating (CVSS 7.4), and does not say whether the flaw has been exploited in GitLab. We will update this when it can be confirmed, and remove this note.

The flaw

The release fixes CVE-2026-132825 (GHSA-34m4-m9fh-gqp5), a heap-based buffer overflow in the case conversion of strings in Ruby, the language GitLab runs on. GitLab says that, under certain conditions, changing the case of a crafted string can cause an out-of-bounds heap write, and that the Ruby security team has said the flaw may allow remote code execution in some scenarios. GitLab shows the severity as Critical, the rating the Ruby team gave in its advisory; MITRE rates the CVE High, with a CVSS score of 7.4. Because the bug is in Ruby rather than GitLab's own code, GitLab takes the severity from upstream.

The new versions also carry the fixes for all the other flaws in the Ruby advisory Multiple vulnerabilities in Regexp and String, which we covered when Ruby 4.0.10, 3.4.13 and 3.3.14 came out.

Affected and fixed versions

  • All versions before 19.4.10: upgrade to 19.4.10.
  • 19.5 before 19.5.8: upgrade to 19.5.8.
  • 19.6 before 19.6.1: upgrade to 19.6.1.

GitLab Dedicated had earlier been protected by internal-only releases 19.5.7 and 19.4.9 with interim mitigations; all of those fixes are included in 19.5.8 and 19.4.10.

Self-compiled installations need an extra step

The fix is a patch to Ruby itself. Official GitLab Linux packages and container images already include the patched Ruby, so upgrading the package or image is enough. Installations built from source are different: GitLab says they must rebuild the Ruby used to run GitLab with Ruby 3.3.14 or 3.4.13, or a later release in the same minor series. Upgrading GitLab's code alone does not fix a self-compiled instance that still runs an older Ruby.

Patch every self-managed instance

Upgrade self-managed instances to the patch for your branch, including any Geo secondary sites. After upgrading a source installation, confirm the Ruby version GitLab reports in the admin area. Instances that cannot be patched today should be kept off the public internet until they are.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in