Independent tech intelligence, checked against primary sources.

TechPulseMind Useful technology.
No manufactured hype.

Git 2.56.1 patches six security flaws, including code execution in recursive clones

Git 2.56.1 patches six flaws, including code execution in recursive clones and memory corruption in merges, with backports to 2.55.1 down to 2.50.2.

Git 2.56.1 patches six security flaws, including code execution in recursive clones

The Git project released Git 2.56.1 on November 10, fixing six security vulnerabilities that range from arbitrary code execution during recursive clones to memory corruption when processing merges or binary patches. Backports are available in Git 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2, according to GitHub staff software engineer Elijah Newren, who wrote the announcement.

If you run Git yourself, or bundle it inside an application, the project recommends moving to 2.56.1 or the patched release for your maintenance series.

What the six CVEs cover

The most serious is CVE-2026-111760. 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 use that gap to swap a submodule’s .git file for a symbolic link pointing at a directory holding malicious configuration or hooks, and Git can then execute attacker-controlled code during a recursive clone. The fix rejects extremely long index entry paths before their lengths can be truncated.

CVE-2026-113408 involves path traversal through a server’s advertised HEAD. When cloning an empty repository over protocol v2, a malicious server can advertise a HEAD symref whose target contains path-traversal components, and a later branch update can then write outside the intended reference directory. Git now validates the advertised target, and other reference names and symref targets received through protocol v2, before accepting them.

CVE-2026-114467 is a stack corruption bug in signature stripping. Git assumed a message would carry at most two GPG signatures, so merging a tag with more than two can write past a fixed-size stack array, causing memory corruption and a possible denial of service. Hosting services that perform such merges on users’ behalf can also be affected. The fix removes the fixed-size array.

CVE-2026-114469 covers out-of-bounds reads when applying binary patches. Git rejects patches larger than roughly 1 GiB, but that check only looked at the supplied size, and a compressed binary patch can expand past the limit and crash Git. Git now also checks the declared uncompressed size.

CVE-2026-105437 is heap corruption during large merges. The memory calculation for a merge result can overflow when the result is very large, including many conflicts combined with a large conflict-marker-size attribute, leading Git to allocate a too-small buffer and write outside it. The fix uses size-appropriate types and checked arithmetic, rejecting merges whose output size cannot be represented safely.

The sixth, CVE-2026-114466, concerns filesystem access through fast-import streams. Three features — rewrite-submodules-from, rewrite-submodules-to and export-pack-edges — lacked the restrictions Git applies to untrusted input streams, allowing arbitrary file reads that could leak contents through error messages, or the creation and appending of files. They are now rejected unless the caller explicitly enables –allow-unsafe-features, which the announcement says should only be used when you trust the program generating the stream.

The release also adds overflow checks to related index entry allocations during checkout and tree processing.

GitHub has already deployed the fixes

GitHub says it has deployed fixes across github.com, GitHub Enterprise Cloud and GitHub Enterprise Cloud with data residency. GitHub Enterprise Server administrators can update to 3.19.15, 3.20.11, 3.21.9 or 3.22.4. Patched versions of Git are also being coordinated for GitHub Desktop, the GitHub Copilot app, GitHub Codespaces and GitHub Actions.

If you cannot update right away, the project suggests cloning only from trusted servers, avoiding recursive clones of untrusted repositories, and steering clear of merging untrusted content or tags or processing binary patches and fast-import streams from untrusted sources. Those precautions, the announcement notes, do not replace installing the fixes.

Patched versions are available from your operating system or Git distributor. Update any application that ships its own copy of Git, along with Git installations used by automation and services that process repositories for users.

Sources

Some links on this page may be affiliate links. If you buy through them we may earn a commission at no extra cost to you. See our affiliate disclosure.