Skip to content
DrCompsSignal / computer news
Menu

Git ships six security fixes, including recursive-clone RCE

Git 2.56.1 and maintained backports fix six vulnerabilities, including remote code execution during recursive clones of malicious repositories.

The Git project has released Git 2.56.1 and coordinated backports for six security vulnerabilities. The set includes a remote-code-execution path in recursive clones, plus path-traversal and memory-safety flaws in other Git operations.

What changed

CVE-2026-111760 can execute attacker-controlled code when a user recursively clones a malicious repository hosted by the attacker. The other fixes cover an advertised-HEAD path traversal, stack corruption while verifying signatures, an out-of-bounds read while applying binary patches, heap corruption during unusually large merges, and filesystem access through crafted fast-import input.

The fixes are available in Git 2.56.1 and in maintained backports 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, and 2.50.2. Applications and hosted services that bundle their own Git executable need to update that embedded copy; updating a system package alone may not replace it.

Practical consequence

Developers, CI operators, package maintainers, code-hosting providers, and desktop tools should inventory the Git binary actually used in each environment and move to a fixed release. Until then, the project’s specific workaround for the recursive-clone flaw is to avoid --recurse-submodules with untrusted repositories and to clone only from trusted sources.

GitHub says GitHub.com, Actions, and Codespaces have been patched. Its fixed GitHub Enterprise Server versions are 3.19.15, 3.20.11, 3.21.9, and 3.22.4. Those product versions are separate from the upstream Git version numbers.

Limits and evidence

The six bugs do not have equal prerequisites or impact. The recursive-clone RCE requires a malicious repository and recursive submodule processing; several of the remaining flaws require specially crafted inputs or unusually large operations. The coordinated announcement does not state that the vulnerabilities are being exploited in the wild.

This is a security and compatibility release, not a performance release. No benchmark claim is involved, and DrComps has not independently reproduced the exploits.