The Git project shipped security releases on November 10, 2026 that fix six vulnerabilities. The most serious, CVE-2026-111760, can let a booby-trapped repository run attacker code on a developer's machine during a recursive clone.
Fixes are in Git 2.56.1 and in backported releases 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. GitHub, which published the details, has already patched its hosted services and released fixed versions of GitHub Enterprise Server. Every developer, CI system and tool that bundles Git should update.
The Six Vulnerabilities
- CVE-2026-111760, code execution on recursive clone: an integer truncation in index handling lets a very long path pass Git's safety checks under one name and then be written under a shorter one. An attacker can use this to swap a submodule's .git file for a symlink to a folder holding hostile config or hooks, which Git may then run.
- CVE-2026-113408, path traversal via HEAD: when cloning an empty repository over protocol v2, Git stored the server's advertised HEAD target for an unborn branch without validating it. A malicious server could plant traversal components so that a later branch update writes outside the refs folder.
- CVE-2026-114467, stack corruption: code that strips GPG signatures expected no more than two of them. Merging a tag with three or more can overrun a fixed stack array, risking memory corruption and crashes, including on hosting services that merge for users.
- CVE-2026-114469, out-of-bounds read: the roughly 1 GiB limit on patches only looked at the patch as supplied. A small compressed binary patch can expand past that limit and crash Git.
- CVE-2026-105437, heap corruption in merges: the size calculation for a merge result can overflow, for example with many conflicts and a large conflict-marker-size attribute, leading to writes past an undersized buffer.
- CVE-2026-114466, file access via fast-import: three options, rewrite-submodules-from, rewrite-submodules-to and export-pack-edges, were not blocked in untrusted streams. They could read arbitrary files or create and append to files.
How the Fixes Work
Git now rejects extremely long index entry paths before their length can be cut short. It validates the HEAD target a server advertises, along with other ref names and symbolic ref targets received over protocol v2.
Signature stripping no longer uses a fixed-size array, so any number of signatures is handled safely. Binary patches are now also checked against their declared uncompressed size, and merge code uses wider types with checked arithmetic, refusing results too large to represent.
The three fast-import options are now refused when they appear in the input stream unless the caller passes --allow-unsafe-features. The release also adds overflow checks to related index allocations during checkout and tree processing.
GitHub Platform Status
- github.com, GitHub Enterprise Cloud and Enterprise Cloud with data residency are already patched.
- GitHub Enterprise Server fixes are in 3.19.15, 3.20.11, 3.21.9 and 3.22.4, and admins are urged to upgrade quickly.
- Patched builds of GitHub Desktop and the GitHub Copilot app are being coordinated.
- Codespaces and GitHub Actions runners will also receive the fixed Git.
What It Means for Developers
The recursive clone flaw is the one to act on first. Many build scripts and onboarding guides use clone with submodules on third-party code, and that single command could now run hostile hooks on a laptop or build agent.
Platform and DevOps teams have extra work. Self-hosted runners, container base images, code review bots and internal Git servers often carry their own Git copy that desktop updates never touch, and these are exactly the systems that merge or apply untrusted content.
Database developers who keep SQL scripts and migration files in Git are affected just as much as application teams. Treat this as a routine but urgent toolchain patch. For more on securing pipelines, see our coverage of secret scanning for GitHub Actions logs.
How to Update
Install Git 2.56.1, or the patched build in your maintenance line, from your operating system packages or Git distributor. Then run git --version to confirm, and update any application that ships its own Git.
If patching must wait, clone only from servers you trust and avoid recursive clones of unknown repositories. Do not merge untrusted tags or content, and do not process binary patches or fast-import streams from unknown sources. These steps reduce risk but do not replace the update.
Conclusion
Git's November 2026 security release closes six bugs ranging from remote code execution to memory corruption and file access. GitHub's own services are already safe, but every local install, runner and bundled copy needs to move to Git 2.56.1 or a matching backport.
Sources
See my articles more often when you search Google.
