The Git project released security updates on November 10, 2026, addressing six vulnerabilities across repository cloning, reference handling, merges, binary patches and imports. The headline risk is CVE-2026-111760, which can allow attacker-controlled code to run when Git recursively clones a specially crafted repository containing submodules. The release is a security patch, not evidence that every Git user was compromised.
The fixes ship in Git 2.56.1 and maintenance versions 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. GitHub says its cloud-hosting environments already received mitigations, while administrators must also check locally installed clients, integrated development environments and automated build systems. A separate GitHub Actions token-theft investigation illustrates why source-control workflows warrant careful security boundaries.
GitHub’s official May 2026 tutorial demonstrates cloning, branching and Git workflows in VS Code. Archival background; it does not demonstrate the newly disclosed vulnerabilities. Credit: GitHub/YouTube.
Recursive clone flaw crosses a trust boundary
Git normally prevents checkout paths from overwriting repository metadata. In the recursive-clone flaw, an extremely long index path can be truncated, producing a mismatch between the validated path and the path written to disk. A malicious repository could thereby replace a submodule’s .git file with a symbolic link to a directory containing attacker-controlled hooks or configuration. When Git later consults that directory, code execution becomes possible.
The remedy rejects oversized index-entry paths before truncation. Exploitation requires an attacker-controlled repository and the relevant recursive-clone workflow; ordinary Git use should not automatically be described as remote code execution. GitLab-related risks also differ: BitcoinVersus.Tech previously covered an actively exploited GitLab server vulnerability, which affects hosting software rather than the same Git clone mechanism.

Five more bugs span references, merges and imports
CVE-2026-113408 concerns a malicious server advertising a specially constructed unborn HEAD reference. Under the files reference backend, a later update could write outside its intended references directory. CVE-2026-114467 concerns stack memory corruption when Git strips more than two GPG signatures from crafted merge content.
Two other flaws affect data-size calculations. CVE-2026-114469 can crash Git when a compressed binary patch expands beyond an approximately 1 GiB processing limit; CVE-2026-105437 can corrupt heap memory during very large merges. Finally, CVE-2026-114466 concerns unsafe file access through features supplied to git fast-import. The patches add validation, checked arithmetic and restrictions on untrusted input. None of the six advisories establishes that attackers are exploiting every affected deployment.
GitHub’s official March 2026 overview covers repository security tools, Dependabot and code scanning. It is contextual training, not a demonstration of the Git 2.56.1 fixes. Credit: GitHub/YouTube.
Who must update Git
GitHub says the fixes are deployed on GitHub.com, Enterprise Cloud and Enterprise Cloud with data residency. GitHub Enterprise Server patches are available in 3.19.15, 3.20.11, 3.21.9 and 3.22.4. At announcement time, GitHub described updates for Desktop and the Copilot app as being coordinated, with Codespaces and Actions also receiving patched Git installations. Those rollout statements are not proof that every client is already current.
Developers can run git --version to identify the Git binary in their current shell, then use their operating-system distributor or application updater for a patched build. Teams should inventory Git embedded inside desktop applications, containers and build workers, especially where workflows process untrusted pull requests or repositories. Recent VS Code agent changes and dependency drift in an MCP server provide related examples of application-level supply-chain exposure.
If patches cannot be installed immediately, GitHub advises avoiding recursive clones from untrusted repositories, untrusted merges, binary patches and fast-import streams. Such precautions reduce exposure but do not replace upgrading. The release announcement provides no confirmed count of exploited systems, so actual compromise rates remain unknown.
Sources and methodology
Primary documentation: GitHub’s November 10 security advisory, the Git maintainer’s coordinated release announcement, and Git’s recursive-clone security advisory. Version numbers, mechanisms and deployment statuses reflect the dated publisher statements. No exploitation campaign or independent incident total is inferred.
Editor’s Note: Six CVE identifiers, affected Git operations, patched version numbers and GitHub Enterprise Server update versions were checked against original Git and GitHub security announcements. The original 1200 × 630 cinematic-anime featured cover illustrates a conceptual developer workstation and is not evidence of an attack. The in-story shield artwork is credited to GitHub. Two official GitHub YouTube tutorials are archival context, not vulnerability demonstrations. Independent in-the-wild exploitation data and end-user playback have not been verified.
Support BitcoinVersus.Tech
Optional 5,000-satoshi contributions support independent reporting. Open the article on a second display and scan the approved original QR code using a compatible Bitcoin wallet. If reading on a phone, save the QR image and import it into a wallet supporting image-based QR scanning. Verify the destination and amount before authorizing payment.

BitcoinVersus.Tech is volunteer-run and aims to provide verifiably accurate technology reporting. Donations are voluntary and Bitcoin transfers are generally irreversible. Confirm recipient 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb and 5,000 satoshis before payment. The reporting is informational, not a warranty of security, technical performance or financial outcomes.

Leave a Reply