The Git and GitLab fixes published on 10 November 2026 remind us that a repository can become dangerous as soon as it is fetched or merged, according to the maintainers’ announcements. Our position: a website’s security must also cover the tools that prepare its updates, especially when they handle external code.
Git and GitLab: what the new versions fix
According to the Git project's announcement, six vulnerabilities affect cloning, merges, binary patches and internal references, among other things. The fixes arrive in Git 2.56.1, as well as in several earlier maintenance releases.
Two flaws deserve business leaders’ attention. CVE-2026-111760 can allow code execution during a recursive clone, which also fetches the submodules associated with the repository. The maintainers state that a submodule can point to a malicious server: the reassuring look of the main repository is therefore not enough.
CVE-2026-105437 concerns merges and can cause a buffer overflow, with writes outside the intended memory. GitLab states that this flaw can allow command execution in Gitaly, its component responsible for repository operations.
GitLab has released the fixed versions 19.3.8, 19.4.6 and 19.5.4. Its announcement states that GitLab.com and GitLab Dedicated are already patched. CERT-FR published an advisory on this vulnerability on 12 November, flagging the risk of remote code execution.
What this means for your business

For a business, the useful question is a concrete one: which machines pull code, from which sources, and with what rights? We suggest starting from this inventory to examine the CI/CD pipeline, the automated chain that tests and prepares releases.
Take an online shop whose changes go through automated tests. Our analysis consists of checking whether this pipeline accepts external contributions, fetches submodules or performs merges. These operations match the situations described by the maintainers; their presence justifies a priority check of the installations concerned.
You also need to distinguish the platform that hosts the repositories from the machines that work on them. GitLab’s announcement about its hosted service covers its own infrastructure. We check separately the runners, which execute automated tasks, the development servers and the containers used for testing.
To gauge the business stakes, we then look at the access available in these environments: site publishing, file storage, technical credentials. The aim is to determine what a compromised machine could reach, depending on its configuration. The risk is not defined by the name of the installed software alone.
Our view: also protect how the site is prepared
We treat this news as a priority maintenance topic whenever untrusted repositories are processed. The front door can be in the workshop, before the shop window. Securing only the public site ignores how its next versions are built.
This does not justify stopping all development indiscriminately. We favour a decision based on the operations actually executed, the origin of the repositories and the rights granted to the tools. A development agent that pulls in external projects deserves, in this analysis, the same attention as an automated script.
We build this check into the technical maintenance that goes with website creation. For a manager, the expected deliverable must stay readable: the environments concerned, the fixes applied and the restrictions still needed. A list of versions with no link to how the site is used does not help anyone decide.
Three checks to start
-
Identify the Git actually being run. We check the versions on runners, development servers and in CI containers. The check covers every environment used by the tasks, then whether a patched package is available from its distribution. We ask for a record of the fix applied, to avoid confusing inventory with resolution.
-
Also fix standalone GitLab installations. GitLab recommends updating them and states that its official Linux packages and images include the patched Git. For a manually compiled installation, its instructions call for rebuilding the Git binaries embedded in Gitaly as well as the separately configured Git installation. We check this point before considering the work complete.
-
Temporarily reduce exposure. While waiting for the fixes, we recommend suspending recursive clones of untrusted repositories. This restriction targets the scenario described for CVE-2026-111760; it does not replace updates against the other flaws. We complete the work with an access review and a test of the usual delivery path.




