Upgrade GitLab to 19.6.1, 19.5.8 or 19.4.10 to remove the Ruby flaw CVE-2026-132825
Summary
On November 18, 2026, the Ruby security team disclosed seven flaws in the Ruby regular expression engine and in the case conversion of strings. It released Ruby 4.0.10, 3.4.13 and 3.3.14 to fix them. The Ruby security team says that it knows of proof-of-concept code that uses some of these flaws for remote code execution.
GitLab includes its own Ruby. On November 20, 2026, GitLab released GitLab CE and EE 19.6.1, 19.5.8 and 19.4.10. GitLab says that:
- These releases fix CVE-2026-132825 (GHSA-34m4-m9fh-gqp5), a heap-based buffer overflow in the case conversion of strings. Under some conditions, changing the case of a crafted string in GitLab can write outside a heap buffer.
- They also fix the other flaws in the Ruby advisory.
- The severity is Critical, from the Ruby advisory. The CVE record gives CVSS 3.1 7.4, High.
- GitLab.com and GitLab Dedicated already run a fixed version. Their customers need no action.
- The releases have no new migrations. A multi-node installation should not need downtime.
Upgrade each self-managed GitLab installation to 19.6.1, 19.5.8 or 19.4.10. GitLab gives no interim step.
Does this apply to you?
You have more exposure if one or more of these statements is true:
- You run self-managed GitLab CE or EE before 19.4.10, 19.5 before 19.5.8, or 19.6 before 19.6.1. This includes the Linux package, the Docker image and the Helm chart.
- You run a self-compiled GitLab with Ruby before 3.3.14, or Ruby 3.4 before 3.4.13. Upgrading GitLab does not change this Ruby.
- You run other Ruby applications on Ruby before 3.3.14, 3.4.0 to 3.4.12, or 4.0.0 to 4.0.9.
GitLab.com and GitLab Dedicated customers are not affected and need no action. GitLab says that GitLab Dedicated was protected earlier by internal releases.