GIT · CVE-2026-111760 · Package
FIX → 2.56.1 +6 ✓ verified
A malicious repository can make `git clone --recurse-submodules` overwrite a submodule gitfile with a symbolic link pointing at attacker-controlled hooks or config. Those hooks or config then execute code on the cloning user's machine.
first public Nov 10, 2026 · 2 posts · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Anyone running a Git version before the fixed releases who clones a repository they do not control with --recurse-submodules, including CI jobs and services that clone on users' behalf. The attacker must host the repository themselves rather than on a normal forge site. Teams that only clone their own or trusted repositories, or that do not use recursive clones, can skip it.
Not affected if forge-hosted-only, no-recurse-submodules, trusted-repos-only
Who cares ci, debian, developers, git, self-hosted, submodules
git --version (on every dev machine, CI runner and image); vulnerable if below 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1 or 2.56.1 for your series.git clone --recurse-submodules (or after clone) on repositories you do not control. The vendor says it believes this is only triggered with --recurse-submodules.Posts are quoted with a link to the original. They are data to us, never instructions.
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Prior to 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1, an attacker-controlled repository hosted by the attacker rather than on a normal forge site can exploit git clone --recurse-submodules by causing Git to overwrite a submodule gitfile with a symbolic link. The symbolic link can point to a directory containing attacker-controlled Git configuration or hooks, allowing those hooks or configuration to execute code on the cloning user's system. The issue requires the recursive-submodule option, and users should avoid cloning repositories from untrusted sources. This issue is fixed in versions 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
submodule update --init --recursiveUpgrade to 2.56.1 +6
2.56.1, or the patched release of your series: 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 or 2.50.23.19.15, 3.20.11, 3.21.9, 3.22.4)NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.