AEGLIX News
A security flaw in Git allows a malicious repository to execute attacker-controlled code on any system that performs a recursive clone with submodules, as reported by The Hacker News. This vulnerability carries the identifier CVE-2026-111760 and originates from an integer truncation within Git's index handling logic. By crafting an exceptionally long path, an attacker can bypass Git's safety validation; the path is subsequently written to disk using a truncated name that the attacker can set to .git. This manipulation enables the replacement of a submodule's .git file with a symbolic link pointing to a directory containing malicious hooks or configuration.
Although Git normally prevents a .git directory from being replaced by a symbolic link, a newly cloned submodule represents its repository as a .git file rather than a directory, which creates the necessary condition for the bypass. The defect impacts recursive clone operations that initialize submodules, permitting an attacker to construct a repository that exploits the path-length truncation to overwrite the .git file pointer. Consequently, arbitrary code execution becomes possible through malicious Git hooks or configuration when the repository is cloned using the --recurse-submodules flag.
The integer truncation occurs when Git processes extremely long path names during index operations. The safety check validates the full path length, but subsequent filesystem operations truncate the name, allowing an attacker-controlled shortened path to resolve to .git. This truncated path then becomes a symbolic link target pointing to attacker-controlled directories containing malicious hooks or configuration files that execute during subsequent Git operations.
Patched releases now reject excessively long paths before truncation can occur. Git addressed the issue in version 2.56.1 and provided corresponding fixes for the 2.50 through 2.55 maintenance series in versions 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, and 2.55.1. GitHub has deployed these fixes to github.com and GitHub Enterprise Cloud, while GitHub Enterprise Server receives the patches in versions 3.19.15, 3.20.11, 3.21.9, and 3.22.4. Updated builds of GitHub Desktop and the GitHub Copilot application are in preparation, and GitHub Codespaces along with GitHub Actions will also receive the corrected Git. As of Tuesday at 19:09 UTC, Git for Windows had not yet issued a release based on Git 2.56.1.
Report prepared 2026-11-10 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.