One merge request can run commands on a self-managed GitLab server. Upgrade to 19.5.4, 19.4.6 or 19.3.8

By George Bailey   Published: 11/17/26   4 min read

GitLab shipped an unscheduled critical patch release on November 10 for a bug in Git, the tool it uses to store and merge code. Under certain conditions, GitLab says, the bug lets an attacker run commands inside Gitaly, the GitLab service that holds the repositories.

Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.

GitLab.com and GitLab Dedicated are already patched. Servers a company runs itself need GitLab 19.5.4, 19.4.6 or 19.3.8, and anything on 16.2 through 19.2 has no fix on its own line.

A crafted .gitattributes file can overflow Git’s merge code (CVE-2026-105437). On self-managed GitLab that can mean commands running where every repository lives. Upgrade to 19.5.4, 19.4.6 or 19.3.8.

A Git merge bug can run commands on self-managed GitLab servers

CVE-2026-105437 is a heap buffer overflow in Git’s three-way merge code. Git adds up the size of the merged output in a 32-bit signed integer. A repository can set a huge conflict-marker-size in its own .gitattributes file, and with enough conflicts the total wraps around, so Git writes past the end of a buffer that is far too small.

Self-managed GitLab 16.2 and later, and any server that merges outside code

Hosting servers run the vulnerable merge code on their own: when a merge request opens, the server test-merges the branch to show whether it merges cleanly. A public write-up on GitHub says any user who can push a branch and open a merge request can crash that merge, and that GitLab’s suggested attributes-file workaround does not work as written. Self-managed servers with open sign-up, or many outside contributors, are the most exposed.

The CVE record scores it 7.5, assuming someone has to act. GitLab labels the release critical because on GitLab the server does the merge itself. No attacks have been reported and it is not in CISA’s exploited catalog, though CISA’s note on the record marks a proof of concept as public.

Upgrade to GitLab 19.5.4, 19.4.6 or 19.3.8 and update Git to 2.56.1

Forward this

For whoever runs our code hosting: GitLab released an urgent fix for a bug that can let someone with a GitLab account run commands on the server that stores our repositories. If we run GitLab ourselves, can we get it onto 19.5.4, 19.4.6 or 19.3.8 this week, and check who can sign up and create projects in the meantime? If we only use GitLab.com, there is nothing to do.

Details

Hunt / verify

Source: GitLab patch release; Git 2.56.1 release notes

Sources

George Bailey

George Bailey is the byline of the CyberExperts editorial desk, the team behind the CyberExperts Daily Brief. The desk covers vulnerabilities, breaches and security news from vendor advisories, CISA alerts and other primary sources, and links those sources in every story. Questions or corrections: [email protected].