CVE-2026-111760: Remote Code Execution in Git Recursive Submodule Cloning
CVE-2026-111760 is a remote code execution vulnerability in Git's handling of recursive submodule clones. An excessively long pathname passes validation before its length is truncated in the 32-bit ce_namelen field, causing Git to write a shorter pathname than the one validated. A crafted repository can exploit this discrepancy to replace a submodule gitfile with a symbolic link targeting attacker-controlled Git configuration or hooks. Subsequent use of that metadata can execute attacker-specified code during cloning.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation executes arbitrary code with the privileges of the user or automation account performing the clone, compromising the confidentiality, integrity, and availability of resources accessible to that account. Developer workstations and CI workers may expose source code, credentials, build artifacts, and other accessible data. Execution occurs during recursive cloning; opening project files or running setup scripts is not required.
Mitigation
If you can’t patch tonight, do this now.
Until patched, clone only from trusted servers and avoid recursive submodule cloning of untrusted repositories. Initially clone unfamiliar projects without recursive submodule initialization, then inspect submodule sources and selected commits before fetching them, resolving relative repository addresses against the parent repository's address. Restrict CI submodule sources to expected repositories. Evaluate unfamiliar repositories in disposable, least-privileged environments without SSH keys, cloud tokens, deployment credentials, or production data. These precautions do not replace patching.
Remediation
Patch, then assume compromise.
Upgrade Git to the fixed release for the installed maintenance line: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, or 2.56.1, or a later patched release. Vendor packages with documented backported fixes are also suitable. The fix rejects excessively long index paths before pathname lengths can be truncated. Update all Git installations, including copies bundled with applications, containers, build images, and automation services; verify vendor advisories and package changelogs rather than relying solely on upstream version numbers.
Exploits
No validated public exploits yet. Hidden: 4 rejected by Mallory's analysis as not a working exploit.
References
Frequently asked questions
- Is CVE-2026-111760 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-111760 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-111760?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-111760.
- Is there a patch for CVE-2026-111760?
- Upgrade Git to the fixed release for the installed maintenance line: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, or 2.56.1, or a later patched release. Vendor packages with documented backported fixes are also suitable.
- How severe is CVE-2026-111760?
- CVE-2026-111760 has a CVSS v3.1 score of 8.0 (High) and an EPSS score of 0.71% (54th percentile) as of Nov 17, 2026.
Recent activity
62 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.