Subscribe
0%
Illustration for: Git 2.56.1 fixes a recursive-clone bug that can run an attacker's code. Six flaws, and what to update first

Git 2.56.1 fixes a recursive-clone bug that can run an attacker's code. Six flaws, and what to update first

The Git project has shipped 2.56.1 and backports for six vulnerabilities, the worst of which (CVE-2026-111760) lets a booby-trapped repository run code on any machine that clones it with submodules. There are no reports of exploitation yet, but developers, CI runners and Git hosting servers should all update.

Listen to this article0:00 / 4:05

The Git project has released Git 2.56.1, plus backported fixes for every series from 2.50 to 2.55, to close six security vulnerabilities. The most serious, CVE-2026-111760, lets a crafted repository execute code on the machine of anyone who clones it recursively with its submodules, according to the project's announcement as reported by The Hacker News and GitHub's accompanying write-up.

Why it matters: git clone --recurse-submodules is something developers, build scripts and CI pipelines run constantly, often against code they haven't vetted. A bug that turns that command into code execution is a supply-chain risk, not just a desktop one. SecurityOnline lists the flaw at CVSS 8.0. None of the reports we read mention exploitation in the wild or a public exploit so far, which leaves a window to patch before that changes.

How the clone bug works

According to The Hacker News and Upwind's write-up, the problem is an integer truncation in how Git handles paths in its index. An extremely long path passes Git's safety checks, then gets written to disk under a shorter name the attacker controls, one that ends in .git.

Git normally refuses to replace a .git directory with a symlink. In a freshly cloned submodule, though, .git is a small file rather than a directory. The attacker uses the truncated path to swap that file for a symlink pointing at a folder of their own hooks and config, and Git then runs those hooks. The fix makes Git reject overly long paths before their length can be truncated.

All six fixes

CVE What it does Who's most exposed
CVE-2026-111760 Code execution during a recursive clone with submodules (CVSS 8.0, per SecurityOnline) Anyone cloning untrusted repos with submodules, CI runners
CVE-2026-105437 Large merge with many conflicts and a big conflict-marker-size attribute overflows a heap buffer (CVSS 7.5, per SecurityOnline) Servers running git merge-tree, e.g. hosting platforms
CVE-2026-113408 Malicious server sends a path-traversal HEAD when you clone an empty repo over protocol v2, letting a later update write outside the refs folder Clients cloning from untrusted servers
CVE-2026-114466 Three fast-import options can read arbitrary files or create and append to them; now blocked unless --allow-unsafe-features is set Tools that import untrusted fast-import streams
CVE-2026-114467 Stripping signatures from a tag with more than two GPG signatures corrupts stack memory (crash) Services that merge untrusted tags
CVE-2026-114469 A binary patch that expands past the ~1 GiB limit triggers an out-of-bounds read (crash) Anyone applying untrusted binary patches

CVE-2026-105437 was assigned by GitLab, The Hacker News reports. If a server reads Git attributes from the repository, anyone who can push a branch and open a merge or pull request could trigger it. BigGo's report says GitLab describes it as reachable for remote code execution through its Gitaly storage layer.

Fixed versions

Line Fixed release
Git (latest) 2.56.1
Git backports 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, 2.50.2
Git for Windows 2.56.1 (released Nov 11, per BigGo)
GitHub Enterprise Server 3.19.15, 3.20.11, 3.21.9, 3.22.4

GitHub says github.com and GitHub Enterprise Cloud are already patched, Codespaces and Actions are getting the fixed Git, and fixes for GitHub Desktop and the GitHub Copilot app were still being prepared at announcement time, according to The Hacker News and BigGo.

What to do

  1. Check your version: run git --version on workstations, build images and runners. Anything below the fixed release for your series needs updating. The backports start at 2.50, so if you're on something older, move to a current release.
  2. Update from your OS or distributor, including Git for Windows and Homebrew/Linux packages, and rebuild container images that bake in Git.
  3. Don't forget bundled copies. IDEs, desktop Git clients and other tools that ship their own Git need their own updates; GitHub Desktop's fix was still pending at announcement.
  4. GitHub Enterprise Server admins: upgrade to one of the versions in the table above.
  5. Until you've patched, the stopgaps GitHub and the Git project recommend are: clone only from trusted servers, don't recursively clone untrusted repositories, don't merge untrusted content or tags, and don't process untrusted binary patches or fast-import streams.
  6. Self-hosted Git servers that can't upgrade yet: The Hacker News reports that adding conflict-marker-size=7 to each repository's info/attributes file, or turning off those merge checks for untrusted repositories, blunts CVE-2026-105437.

What to watch: whether a proof of concept appears for CVE-2026-111760, since one poisoned repository can reach every machine that clones it, and when GitHub Desktop and other Git-bundling apps ship their updates.

Sources

  1. The Hacker News — Git patches flaw that lets malicious repositories execute code during recursive clones thehackernews.com
  2. SecurityOnline — Git 2.56.1 patches six security flaws including recursive clone code execution securityonline.info
  3. BigGo Finance — Git for Windows v2.56.1 released, fixes six vulnerabilities finance.biggo.com
  4. Upwind — CVE-2026-111760: Git recursive clone integer truncation enables submodule gitfile symlink RCE upwind.io
  5. daily.dev — Git security vulnerabilities announced (summary of GitHub's write-up) daily.dev

#Git#CVE-2026-111760#CVE-2026-105437#GitHub#GitLab#Git for Windows#submodules#supply chain#patch now