Recursive cloning is the convenience nobody checks. Git walks the submodules and pulls them one after another, because someone asked it to. That is exactly where the heaviest of the six holes sits, the ones Git just shipped fixes for.
Fact
The facts: on 10 November 2026 the Git project announced six vulnerabilities and released the fixes in Git 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. CVE-2026-111760 is code execution during recursive clones: an integer truncation in Git's index handling lets an extremely long path pass validation under one name and then be written under a shorter one. An attacker can replace a submodule's .git file with a symbolic link to a directory holding malicious configuration or hooks. CVE-2026-113408 is path traversal through a server's advertised HEAD: a malicious server supplies a name containing path-traversal components. CVE-2026-114467 is stack corruption when removing signatures: a message with more than two signatures makes Git write past the end of a fixed-size stack array. CVE-2026-114469 is out-of-bounds reads when applying binary patches: a patch larger than approximately 1 GiB is rejected, but the check only looks at the size as supplied, and a compressed patch can expand beyond it. CVE-2026-105437 is heap corruption during large merges: the memory calculation can overflow and Git writes outside the buffer. CVE-2026-114466 is filesystem access through fast-import streams: rewrite-submodules-from and rewrite-submodules-to can read arbitrary files, and export-pack-edges can create files or append data to existing ones. According to GitHub, the fixes are deployed across github.com, GitHub Enterprise Cloud and GitHub Enterprise Cloud with data residency, and for GitHub Enterprise Server the updates are in 3.19.15, 3.20.11, 3.21.9 and 3.22.4.
The fix for the heaviest one is boring and exact: it rejects extremely long index entry paths before their lengths can be truncated. The other five follow the same shape. The check comes before the write, not after.
The check and the write carry different names. The difference between them is exactly where the hole hides.
There is also one switch worth knowing: --allow-unsafe-features. The three dangerous fast-import features are rejected unless you turn it on explicitly. Turn it on only when you trust the program generating the stream.
If you cannot update right away: clone only from trusted servers and avoid recursive clones of untrusted repositories. Do not merge untrusted content or tags. Do not process binary patches or fast-import streams from an untrusted source. These precautions do not replace the fix.
Update to 2.56.1 or to the patched release for your series. The version is the easy part. The hard part is remembering how many things on your machine carry their own copy of Git.
Official primary sources
Git project - Git security vulnerabilities announced, 10.11.2026The visual is generated code-art, no third-party images.