Skip to content

Git 2.56.1 patches a code-execution bug in recursive clones

A symlink swap in a malicious submodule can run attacker code during git clone --recursive, one of six security bugs fixed; five older maintenance lines get the same patch.

Source: GitHub

Git 2.56.1 shipped on 10 November, fixing six security bugs, the worst a code-execution flaw triggered by a recursive clone of a malicious repository. CVE-2026-111760 is an integer truncation bug in Git’s index handling: an attacker can swap a submodule’s .git file for a symlink pointing at a directory with rogue hooks or configuration, and Git runs that attacker-controlled code during the clone.

The other five cover a path-traversal bug via a server’s advertised HEAD (CVE-2026-113408), stack corruption when a merged tag carries more than two GPG signatures, heap corruption from oversized conflict markers during a merge, an out-of-bounds read in binary patches, and unchecked file reads and writes through fast-import streams. Backports cover 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2, so there’s a patched release for every maintained line.

Why it matters: git clone --recursive on an untrusted repository, something CI pipelines and open-source contributors do routinely, is the exact scenario the worst bug targets. Anything that bundles its own copy of Git, an IDE, a CI image, a package manager, needs its own update, not just your system Git.

The caveat: if you can’t upgrade immediately, only clone recursively from sources you trust, and avoid merging tags, applying binary patches or processing fast-import streams from anyone you don’t.

Share

Related reading

More from The Wire

All briefs