• Sources: primary, discussion
  • Summary: The Git project released 2.56.1 with backports to 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. CVE-2026-111760 uses an integer truncation in index handling to replace a submodule's .git file with a symlink and run attacker hooks during a recursive clone, and other fixes cover path traversal through a server's advertised HEAD, stack and heap corruption in signature stripping and large merges, binary patch out-of-bounds reads, and unsafe git fast-import stream features. GitHub has patched github.com and shipped GitHub Enterprise Server 3.19.15, 3.20.11, 3.21.9 and 3.22.4.
  • Why it matters: Update Git on workstations, CI images and any service that bundles Git, and treat servers that merge or apply patches from untrusted users as exposed to the merge and patch memory bugs.
  • Background: A recursive clone also clones each submodule, and a submodule's .git entry is a file that points at its repository metadata. Git refuses to write paths that would overwrite that metadata because a repository's config and hooks can run commands. Several past Git advisories have used the same pattern of tricking checkout into writing into a .git location. Forges are affected separately from clients because they run merges and patch application on content that users push.
  • Follow-up: Distribution packages, updates to tools that bundle Git, and any exploitation reports.