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.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
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.
- GitLab: CE and EE from 16.2 before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Fixed November 10.
- Git: fixed in 2.56.1 and the backports 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2, which also fix five other Git flaws, including recursive-clone code execution (CVE-2026-111760).
- Source installs: GitLab says to rebuild the Git inside Gitaly and also the Git that
git.bin_pathpoints to, or move that one to 2.56.1 or a distribution build patched for this CVE.
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
- Check your version on the admin Help page, or run
sudo gitlab-rake gitlab:env:info. Upgrade to 19.5.4, 19.4.6 or 19.3.8 or later. Servers on 16.2 to 19.2 need a planned upgrade along GitLab’s upgrade path. - On clusters, confirm every Gitaly node took the new build.
- On source installs, rebuild Gitaly’s Git and the Git at
git.bin_path, as GitLab’s release notes describe. - Until you are patched, turn off open sign-up or require admin approval, and limit who can create projects.
- Update Git to 2.56.1 or your distribution’s patched build on CI runners and build servers that merge or rebase outside branches.
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
- CVE-2026-105437: heap-based buffer overflow (integer overflow in the xdiff merge size calculation). CNA: GitLab. CVSS 3.1: 7.5 (AV:N/AC:H/PR:N/UI:R). Published November 10, 2026. NVD status: deferred.
- GitLab advisory: GitLab Critical Patch Release 19.5.4, 19.4.6, 19.3.8 (November 10, 2026). Reported through HackerOne.
- Git: 2.56.1, 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2 fix CVE-2026-105437 along with CVE-2026-111760 and four more.
- Exploitation: none reported by GitLab; not in CISA’s KEV catalog as of its November 13 update. CISA’s ADP note on the CVE record lists exploitation as “poc”. Status: THEORETICAL.
Hunt / verify
- Load GitLab’s detection for a
git merge-treechild process crash (published in its TLDR detection project) and run it against Gitaly and Sidekiq logs going back to when the server ran an affected version. - Search recently pushed branches for .gitattributes files that set
conflict-marker-sizeto an unusually large number. - Treat a hit as an attempt to run code on Gitaly: review recent pushes, new deploy keys and CI/CD variables that hold cloud credentials.
Source: GitLab patch release; Git 2.56.1 release notes
Sources
- GitLab: Critical Patch Release 19.5.4, 19.4.6, 19.3.8
- NVD: CVE-2026-105437
- GitHub Advisory Database: CVE-2026-105437 (Git)
- Git: v2.56.1 release notes
- GitLab Security: TLDR detection rules
- GitHub: googlesky/CVE-2026-105437 write-up
- Cohash: GitLab’s off-cycle Git fix explained
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.