Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitywidely-deployed-product-advisoryinternet-facing-service-vulnerability

GitLab Patches Git Heap Overflow That Could Enable Command Execution in Gitaly

Vulnerability Disclosure · 7 sources · Updated 6d ago · First seen Nov 10, 2026

GitLab Patches Git Heap Overflow That Could Enable Command Execution in Gitaly

GitLab released Community Edition and Enterprise Edition versions 19.5.4, 19.4.6, and 19.3.8 to address CVE-2026-105437, a heap-based buffer overflow in bundled Git. Size calculations for very large merge results can overflow, producing an undersized buffer and out-of-bounds heap writes; under certain conditions, the flaw could allow arbitrary command execution within GitLab’s Gitaly environment. GitLab credited researcher taise with reporting the vulnerability through its HackerOne bug bounty program. Amazon Linux rates the vulnerability Important, with a CVSS v3 score of 7.5, and lists fixes as pending for Amazon Linux 2, Amazon Linux 2023, and Amazon Linux 2027 Preview.

GitLab strongly recommends immediately upgrading affected self-managed installations; GitLab.com and GitLab Dedicated are already patched and require no customer action. Official GitLab Linux packages and container images include patched Git, while self-compiled deployments require additional steps to rebuild the Git binaries used by Gitaly and GitLab or install appropriately patched distribution packages. The releases contain no new migrations and should not require downtime for multi-node deployments, although Omnibus packages restart services by default during upgrades.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

7 events · Nov 10, 2026
  1. Reported Nov 10, 20268d ago

    Upstream Git releases fixes for CVE-2026-105437 across maintenance branches

    Upstream Git announced fixed releases 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1. The fixes replace vulnerable merge-output size calculations with appropriately sized types and checked arithmetic, rejecting oversized results where necessary.

    Overview of CVE-2026-105437: Heap Buffer Overflow in Git's xdiff Three-Way Merge via Oversized Conflict Markers - ZeroPath Blog | ZeroPath
  2. Nov 10, 20268d ago

    CVE record discloses Git merge overflow trigger and mitigations

    The published CVE-2026-105437 record detailed how attacker-controlled .gitattributes settings and multiple merge conflicts can overflow output-size calculations, causing an undersized heap allocation and out-of-bounds writes. It also described exposure through server-side mergeability checks, overflow-checked patches, and workarounds that override conflict-marker-size or disable checks for untrusted repositories.

    CVE Record: CVE-2026-105437
  3. Nov 10, 20268d ago

    Amazon Linux publishes CVE-2026-105437 assessment with fixes pending

    Amazon Linux made its CVE-2026-105437 assessment public, rating the vulnerability Important with a CVSS v3 score of 7.5. It described overflowing size calculations for very large merge results leading to heap corruption and listed Git fixes as pending for Amazon Linux 2, 2023, and 2027 Preview.

    CVE-2026-105437
  4. Nov 10, 20268d ago

    GitLab releases critical security updates for CVE-2026-105437

    GitLab released CE and EE versions 19.5.4, 19.4.6, and 19.3.8, updating bundled Git to remediate CVE-2026-105437. It urged affected self-managed customers to upgrade immediately and specified additional Git rebuild or package-update steps for self-compiled installations.

    GitLab Critical Patch Release: 19.5.4, 19.4.6, 19.3.8 | GitLab Docs
  5. Reported Nov 10, 20268d ago

    GitLab patches GitLab.com and GitLab Dedicated

    GitLab patched GitLab.com and GitLab Dedicated against CVE-2026-105437. Customers of these hosted services were told no action was required.

    GitLab Critical Patch Release: 19.5.4, 19.4.6, 19.3.8 | GitLab Docs
  6. Reported Nov 10, 20268d ago

    Researcher taise reports Git heap overflow through GitLab's bug bounty program

    Researcher taise reported CVE-2026-105437 through GitLab's HackerOne bug bounty program. The heap-based buffer overflow could, under certain conditions, enable arbitrary command execution within GitLab's Gitaly environment.

    GitLab Critical Patch Release: 19.5.4, 19.4.6, 19.3.8 | GitLab Docs
  7. Reported Oct 23, 202626d ago

    Report describes successful GitLab code execution via Git merge overflow

    A technical report states that CVE-2026-105437 was successfully exploited to achieve remote code execution through the Git process launched by Gitaly for GitLab mergeability checks. The attack used repository-controlled attributes and conflicting branches; the report does not claim exploitation in the wild.

    [CVE-2026-105437] Heap buffer overflow in xdiff three-way merge via large conflict-marker-size (#814) · Issue · gitlab-org/git
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

5 linked
GitlabAmazon LinuxGitGitlab Community EditionGitlab Enterprise Edition

Organizations

1 linked
GitLab
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.