Skip to content
GitLab patches Ruby heap overflow CVE-2026-132825 in self-managed Community and Enterprise Editions
Black Shard

Loading

    AdvisoriesHigh severity

    GitLab patches Ruby heap overflow CVE-2026-132825 in self-managed Community and Enterprise Editions

    GitLab states the fix is a patch to Ruby, so its packages and container images carry it while self-compiled installations must rebuild Ruby. It states GitLab.com and GitLab Dedicated customers do not need to take action.

    Black Shard Advisories

    2 min read

    Share

    Affects

    GitLab Community Edition

    What to do

    Upgrade every self-managed GitLab instance to a fixed release today, internet-facing instances first.

    On this page
    1. How the flaw works
    2. What to do now
    3. Who is affected
    4. Detection notes
    5. Essential Eight mapping
    Advisory BS-ADV-2026-0019
    Vendor advisory
    CVE
    CVE-2026-132825
    CVSS
    7.4 (v3.1, MITRE)
    Exploitation
    None known
    Affected
    • GitLab Community Edition and Enterprise Edition (self-managed)
    • All versions before 19.4.10
    • 19.5 before 19.5.8
    • 19.6 before 19.6.1
    Fixed in
    • 19.6.1
    • 19.5.8
    • 19.4.10
    • Ruby 3.3.14 or 3.4.13 (self-compiled installations)

    How the flaw works

    Changing the case of a crafted string can write one byte outside a heap buffer in Ruby, for example with ISO-8859-1 or Windows-1252 text. GitLab states the overflow is reachable in GitLab under certain conditions, and the Ruby security team has stated it may allow remote code execution in some scenarios.

    What to do now

    Check how each instance was installed before touching it: GitLab states its Linux packages and container images already include the patched Ruby, while self-compiled installations must rebuild Ruby.

    1. List every self-managed GitLab instance and whether it runs from official packages, container images or source
    2. GitLab states these versions add no new migrations and should need no downtime on multi-node deployments
    3. GitLab states Omnibus packages stop, run migrations and start again by default unless /etc/gitlab/skip-auto-reconfigure exists
    4. Upgrade packaged and container installs to the fixed release for their branch
    5. On self-compiled installs, rebuild the Ruby that runs GitLab with a fixed Ruby release
    6. Update other applications on the same hosts that run their own Ruby, since NVD records the flaw in Ruby

    Who is affected

    GitLab names no particular deployment type, which under its own guidance means every type of self-managed Community Edition and Enterprise Edition is affected. GitLab states GitLab.com and GitLab Dedicated customers do not need to take action.

    Detection notes

    The evidence sits on the GitLab host. Review its application and system logs from 19 November 2026, when NVD published the record, onwards.

    • Ruby worker processes on the GitLab host crashing or restarting with no known cause
    • Shells or other child processes started by the GitLab service account
    • Access tokens, deploy keys or administrator accounts nobody on the team created

    Essential Eight mapping

    Patch applications: the Essential Eight Maturity Model sets 48 hours from release to patch internet-facing services when the vendor rates a vulnerability critical, and GitLab carries the Ruby security team's critical rating for this fix. Restrict administrative privileges and application control limit what code running as the GitLab service account can reach.

    Affected by this advisory?

    Tell us what you run. We patch, contain and check for signs of compromise.