CVE-2026-111760
🟠 MediumGit — submodule handling during clone --recursive · Fixed in 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. The affected range is not stated by the project, so anything below those lines should be treated as affected
54.28th percentile
Exploitation
Timeline
- 10/11/2026Git patches flaw letting a malicious repo execute code via submodule symlink trick
- 11/11/2026Git RCE via malicious recursive clone
- 16/11/2026CVE record published (CVE List)
Risk
.git file with a symbolic link to a directory holding attacker-controlled configuration or hooks, giving code execution during a recursive clone)Fix
--recursive is often the default in build scriptsOfficial description
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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
CWE-59