Git 2.56.1 fixes six vulnerabilities, including code execution when recursively cloning a malicious repository
The Git project released 2.56.1 on November 10 with backports across six maintenance branches, fixing six vulnerabilities, one of which allows a malicious repository to run attacker code during a recursive clone, with GitHub already patching its hosted services.
The Git project released security updates on November 10 in version 2.56.1, fixing six vulnerabilities, with backports shipped for the 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2 maintenance series.
The most serious is CVE-2026-111760, whose root cause is an integer truncation in how Git handles its index: an extremely long file path can pass the safety check under one name and then be written to disk under a shorter name the attacker controls. Exploiting this difference lets an attacker replace a submodule's .git file with a symbolic link pointing at a directory containing malicious configuration or hooks, which Git then executes during a recursive clone, and GitHub's advisory rates it high severity. The other five are CVE-2026-113408, a path traversal when cloning an empty repository via a server-advertised symbolic HEAD reference; CVE-2026-114467, stack corruption when stripping more than two GPG signatures; CVE-2026-114469, an out-of-bounds read because the roughly 1GB binary patch size check only inspected compressed input; CVE-2026-105437, a buffer size calculation overflow during merges with many conflicts; and CVE-2026-114466, where three fast-import features could read or write files outside the repository.
GitHub said it has deployed fixes across its hosted services, and that GitHub Enterprise Server administrators should upgrade to 3.19.15, 3.20.11, 3.21.9 or 3.22.4, with Codespaces and Actions also receiving fixed versions. GitHub engineers advise installing the patched release for your series and updating any software that bundles its own copy of Git; if that is not immediately possible, clone only from trusted servers, avoid recursive clones of untrusted repositories, avoid merging untrusted content or tags, and avoid processing binary patches or fast-import streams from untrusted sources.