On this page (8 sections)

The Git project has released security updates for six vulnerabilities. The most serious, CVE-2026-111760, can let a malicious repository run an attacker's code on a computer that clones it recursively, meaning together with its submodules, according to The Hacker News and Help Net Security.

Anyone who runs git on a laptop, a build server, a CI runner or a code-hosting service should care, especially if those systems ever clone repositories they do not control. The details below come from press reporting, because no original vendor advisory or NVD record was available to us when this was written.

What happened

The Git project shipped Git 2.56.1 together with fixes for the 2.50 through 2.55 series. The headline bug is an integer truncation in how Git handles its index. Reporting describes it as a path-length confusion: a path that is extremely long passes a safety check, then is written to disk under a shorter name.

GitHub says it has already deployed fixes on github.com, GitHub Enterprise Cloud and GitHub Enterprise Cloud with data residency. Patched builds for GitHub Desktop and the GitHub Copilot app are being coordinated, and Codespaces and Actions will receive them too, per Help Net Security.

How the recursive clone flaw works

Git refuses to replace a .git directory with a symbolic link. In a freshly cloned submodule, however, .git is a file, not a directory. The reported attack uses the path mismatch to give an entry the name .git, replacing a submodule's .git file with a symbolic link that points to a folder containing attacker-chosen configuration or hooks.

Hooks are programs Git runs at defined points in its workflow. Once Git follows the link and uses that folder, the attacker's code can run under the account doing the clone. The fix rejects overly long index paths before their length can be truncated. We are not describing exploitation steps, and we have not seen a primary advisory to confirm finer technical details.

The five other vulnerabilities

The same releases fix five more issues, as summarized by the two reports:

Other flaws fixed alongside CVE-2026-111760 (as reported)
CVEAreaReported impact
CVE-2026-113408Cloning an empty repo over protocol v2A malicious server can send a branch name with path traversal, so a later update with the files reference backend writes outside the reference directory
CVE-2026-114467GPG signature strippingA message with more than two signatures overflows a stack array; memory corruption or crash, for example when merging a crafted tag
CVE-2026-114469Binary patchesA small patch can expand past the roughly 1 GiB limit when decoded, causing an out-of-bounds read and a crash
CVE-2026-105437Merge machineryVery large merge results can overflow a size calculation and corrupt heap memory. GitLab assigned this CVE
CVE-2026-114466git fast-importThree features could read arbitrary files or create and append to files. Now rejected from input streams unless --allow-unsafe-features is set

Who is affected

  • Developers who clone third-party or unreviewed repositories with submodules, for example when evaluating a dependency.
  • CI/CD runners and automation that clone repositories on behalf of others, including pull request builds.
  • Code-hosting servers. GitLab said servers are most likely to be targeted through git merge-tree, which may run to check whether a merge request can be merged. If the server reads attributes from the repository, any user who can push branches and open a merge request could trigger CVE-2026-105437.
  • Hosting services that merge on behalf of users, which may be exposed to the GPG signature issue (CVE-2026-114467).
  • Any application that bundles its own copy of Git, which the maintainers say should be updated too.

How to check your exposure

First find out which Git versions you run. On any machine, this read-only command prints the installed version. Compare it with the fixed releases listed above.

Print the installed Git version (any Linux, macOS or Git Bash)Shell
git --version

On Debian or Ubuntu, this shows the installed and candidate package versions. Distributions often backport fixes without changing the upstream version number, so check your vendor's security notice before concluding a build is vulnerable.

Show installed and available git package versions (Debian/Ubuntu)Shell
apt-cache policy git

On RHEL-family systems, the following lists the installed package and its changelog entries, where you can look for the CVE identifiers.

Check the installed git package and search its changelog for the CVE (RHEL, Fedora, CentOS)Shell
rpm -q git
rpm -q --changelog git | grep -i CVE-2026-111760

Also inventory tools that ship their own Git, such as desktop clients, IDE plugins and build images, since a system update will not touch them.

What to do now

Caution. Updating Git on a shared build server or hosting service can interrupt running jobs. Schedule the change and restart any long-running services that call Git afterwards.
  1. Install Git 2.56.1, or the patched release for your series (2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 or 2.50.2), from your operating system or Git distributor.
  2. Update CI runners, container images and any software that bundles its own copy of Git.
  3. On Windows, watch for a Git for Windows release based on 2.56.1, which had not appeared when The Hacker News checked.
  4. If you run GitHub Enterprise Server, upgrade to 3.19.15, 3.20.11, 3.21.9 or 3.22.4.
  5. If you run a code-hosting server that cannot upgrade yet, GitLab's workaround for CVE-2026-105437 is to add conflict-marker-size=7 to each repository's info/attributes file, or turn off merge checks for untrusted repositories.
  6. Until patched, clone only from trusted servers, avoid recursive clones of untrusted repositories, and do not merge untrusted content or tags or process untrusted binary patches or fast-import streams.
  7. Only pass --allow-unsafe-features to git fast-import when the program generating the stream is trusted.
Elijah Newren of GitHub said these interim precautions do not replace installing the fixes.

On Debian or Ubuntu, the usual update path for the package is shown below. It upgrades only git and its dependencies and does not remove anything.

Update only the git package (Debian/Ubuntu)Shell
sudo apt-get update
sudo apt-get install --only-upgrade git
Update only the git package (RHEL, Fedora, CentOS)Shell
sudo dnf upgrade git

Detection and monitoring afterwards

The sources do not describe indicators of compromise or any observed attacks, so there is no known signature to hunt for. Reasonable review steps are to look at CI jobs that recursively cloned unfamiliar repositories before you patched, check those runners for unexpected processes or changed credentials, and rotate secrets that were available to such jobs if anything looks odd.

Treat build systems as part of your attack surface. Our guide to website security for small business covers the basics, and the Webforta Monitor page describes uptime, certificate and DNS change monitoring for the sites you run. Keep track of other recent patches in the Webforta blog.

What we do not know yet

  • There is no NVD record or CVSS score for CVE-2026-111760 yet, so its official severity is unrated.
  • We did not find the Git project's own release announcement or GitHub's write-up in our research, only reporting that links to them. Check those primary sources for the latest details.
  • Neither report states that any of the six flaws is being exploited.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. Git fixes six vulnerabilities, including code execution during recursive clones - Help Net Securityhelpnetsecurity.com ·
  2. Git Patches Flaw That Lets Malicious Repositories Execute Code During Recursive Clonesthehackernews.com ·
  • Git
  • CVE-2026-111760
  • Supply chain
  • Submodules
  • Patch now