StepSecurity, maker of the Harden-Runner tool used by more than 20,000 open-source projects, announced a US$20 million Series A led by Elephant to protect developer machines, package downloads, CI/CD pipelines and agent sandboxes.
GitLab critical patch 19.6.1, 19.5.8 and 19.4.10 fixes Ruby heap overflow
EditorialBy 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
- GitLab Critical Patch Release: 19.6.1, 19.5.8, 19.4.10, 20 November 2026
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.
You may be interested in
nginx released mainline 1.31.9 and stable 1.30.7 on 18 November 2026 with fixes for ten vulnerabilities, three rated major: HTTP/2 flow-control memory corruption, a TLS 1.3 request-body loop and a mail proxy use-after-free.
Versions 1.26.1 and 1.26.2 of the agent-framework package on PyPI, published on 17 November 2026 and since removed, carried a credential stealer that ran at every Python start; anyone who installed them should rotate their secrets.
CISA added CVE-2026-115731, a deserialization flaw in Puppet report processing that lets an agent certificate holder run code on Puppet Server, to the KEV list on 17 November 2026; fixed in Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13.
GitHub Enterprise Server 3.22.5, 3.21.10, 3.20.12 and 3.19.16, released on 17 November 2026, fix a list of high-severity flaws, from pre-receive hook sandbox escapes and SSH certificate checks to command injection in GitHub Pages.
Chainguard now lists a free Starter plan with no end date and a $500 a month Team plan paid by credit card, alongside custom Enterprise pricing, with limits on images, downloads and dependency pulls.
Bulletin 2026-186 covers amazon-efs-utils before 3.3.5; 2026-187 covers aws-privateca-issuer before 1.12.0, which stops cross-namespace credential use and so needs issuers migrated before upgrading.
From 21 December 2026 Heroku Automated Certificate Management issues ECDSA P-256 keys instead of RSA, migrating apps in stages to 29 January 2027; apps with older clients can opt out.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More CybersecurityThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.