Git fixed six bugs across seven release lines. Recursively cloning a repository hosted by an attacker can run code on the cloning host. Other flaws affect untrusted refs, tags, merges, binary patches and fast-import streams.
Git’s November release addresses a code execution path where a very long index entry passes path validation under one name and is written under a truncated name. In the recursive-clone path the write can replace a submodule’s gitfile with a symlink. The code then runs with the privileges of the user or job performing the clone. The maintainer describes a repository hosted by the attacker and a recursive clone using --recurse-submodules. A top-level repository on a familiar forge can still point to a malicious submodule on a different host through .gitmodules.
GitHub reports fixes on GitHub.com and GitHub Enterprise Cloud, including data residency. Its November 10 announcement lists GitHub Enterprise Server updates separately and describes patched Git for Actions, Codespaces, GitHub Desktop and the Copilot app as forthcoming. Verify the installed version in the environment where Git actually runs. Distribution packages may carry backported fixes under different package versions. The maintainers identify affected releases back to 2.27.0 and provide no upstream maintenance releases for branches below 2.50. Migrate older installations or verify a fix with the distributor that maintains your build.
The other five vulnerabilities have distinct inputs. For example, an attacker can trigger the three-way merge flaw through a service that checks mergeability using attributes from the proposed tree. Avoid untrusted inputs until the relevant service has been updated.
CVE-2026-111760A crafted path can overwrite the submodule gitfile with a symlink to attacker-controlled Git configuration or hooks. The maintainer describes an attacker-hosted repository cloned with --recurse-submodules.
When cloning an empty repository from a malicious protocol v2 server with the files reference backend, Git can store a malformed unborn HEAD target. A later branch update can write outside the reference directory.
Merging a crafted tag with more than two GPG signatures can corrupt the stack and crash Git, including on a service that performs that merge.
Applying a compressed binary patch with an oversized expanded form can bypass the input limit and crash Git.
Large merge output can overflow a size calculation. A crafted conflict-marker-size can amplify it when the operation reads attributes from the relevant tree.
Untrusted stream directives can read files through submodule mark rewriting or create and append to files through export-pack-edges. Patched Git gates them behind --allow-unsafe-features.
| Product | Safe from | Note |
|---|---|---|
| Git 2.56 | 2.56.1 | |
| Git 2.55 | 2.55.1 | |
| Git 2.54 | 2.54.1 | |
| Git 2.53 | 2.53.1 | |
| Git 2.52 | 2.52.1 | |
| Git 2.51 | 2.51.3 | |
| Git 2.50 | 2.50.2 |
Nov 10, 2026
Git publishes six fixes
Git 2.56.1 and six maintenance releases are available. GitHub reports hosted-service fixes and lists GitHub Enterprise Server updates.
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.