A malicious repository can run an attacker's code on any machine that clones it recursively. This is the consequence of CVE-2026-111760, an integer truncation in how Git handles its index. The Git project fixed it in Git 2.56.1, with backports for the 2.50 through 2.55 series. For third-party risk management (TPRM) practitioners, the flaw is a test of how quickly your organization can identify and patch a tool embedded in nearly every engineering workflow.
This case study examines the technical issue directly, focusing on the response decisions your team can learn from.
Understanding the Challenge
Git may not seem like a third party. It's a free command-line tool that developers install and forget. However, it executes code from repositories you don't control, making it a supply chain entry point.
The mechanics are crucial for risk scoring. An extremely long path in a repository can bypass Git's safety check, then be written to disk under a shorter name that an attacker can set to .git. This allows the attacker to replace a submodule's .git file with a symbolic link pointing to malicious hooks or configurations. Hooks are programs Git runs at set points, so once Git uses that folder, the attacker's code runs.
The submodule detail is key. Git refuses to replace a .git folder with a symbolic link, but in a freshly cloned submodule, .git is a file. The safeguard exists; the flaw bypasses it.
Your challenge isn't understanding the exploit chain. It's that the patch isn't a single update. Fixed versions span multiple release lines, and every product that bundles its own Git copy needs its own fix.
Environment and Constraints
Consider how patch availability looked after disclosure. You can't patch what your vendors haven't shipped.
- The Git project released 2.56.1 plus fixes for 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, and 2.55.1.
- GitHub applied the fixes to github.com and GitHub Enterprise Cloud. For GitHub Enterprise Server, fixes landed in 3.19.15, 3.20.11, 3.21.9, and 3.22.4.
- Fixed versions of GitHub Desktop and the GitHub Copilot app were still being prepared. GitHub Codespaces and GitHub Actions were also slated to receive the fixed Git.
- Git for Windows hadn't released a version based on Git 2.56.1 as of Tuesday at 19:09 UTC, according to The Hacker News.
Your exposure was uneven by platform. Hosted services were fixed by the provider. Self-hosted servers required your action. Desktop clients and Windows builds were waiting on upstream. A single "we patched Git" statement would have been incorrect for most enterprises.
Five other flaws shipped in the same releases, including path traversal on empty-repository clones (CVE-2026-113408), memory corruption from tags with more than two GPG signatures (CVE-2026-114467), and an out-of-bounds read from oversized binary patches (CVE-2026-114469). Bundling raises the cost of delay, as one upgrade closes six issues.
Recommended Approach
GitHub's advice sets the response order. Install a fixed version from your operating system or Git distributor, and update any application that ships its own copy of Git. Until then, apply interim controls that, in GitHub's words, don't replace the fixes:
- Clone only from servers you trust.
- Don't recursively clone repositories you don't trust.
- Don't merge content or tags you don't trust.
- Don't process binary patches or fast-import streams from sources you don't trust.
Translate this into a TPRM workflow in three layers.
Inventory First. The "update any app that ships its own copy of Git" instruction is a Fourth and Nth Party Management problem. IDEs, CI runners, desktop clients, and build agents may each carry an embedded Git. Your software inventory needs to record bundled components, not just standalone installs. Continuous Monitoring of Active Arrangements should flag Git versions below the fixed releases and alert when a vendor's product advisory changes.
Trust Boundaries Second. The interim controls are essentially a source-trust policy. Define which repositories your build systems may clone recursively, and block the rest. Treat submodule references in third-party code as a Pre-Contractual Assessment item when you adopt a dependency, since a submodule is a dependency you didn't explicitly review.
Server-Side Exposure Third. GitLab, which assigned CVE-2026-105437, noted that code-hosting servers are most likely to be targeted through git merge-tree, which a server may run to check whether a pull or merge request can be merged. If a server reads the conflict-marker-size attribute from a repository's .gitattributes, any user who can push branches and open a pull or merge request can trigger the flaw. Servers that can't upgrade can add conflict-marker-size=7 to each repository's info/attributes file, or turn off those merge checks for untrusted repositories.
Results and Metrics
This is an ongoing event, so there are no remediation outcomes to report. What can be stated is the state of the patch landscape: provider-managed services were being fixed centrally, while self-managed and client-side software depended on vendor release timing. Your metric set should track time from advisory to fixed version deployed, by platform class, and the count of embedded Git copies still unpatched.
What You'd Do Differently
Three gaps tend to surface in events like this.
- Treating Git as Out of Scope. Free developer tooling often escapes Criticality Classification. A tool that executes repository-supplied hooks deserves a tier based on what it can reach, not what it costs.
- Relying on One Patch Owner. With fixes split across the project, GitHub's services, and downstream distributors, you need named owners per channel.
- Waiting for a Clean Fix. The interim controls cost little. Apply them while you wait for vendors like Git for Windows to ship.
Takeaways for Your Team
- Map every embedded Git copy; the version on a developer laptop isn't the only one that matters.
- Write a source-trust rule for recursive clones and enforce it in CI.
- Split your response by platform: hosted, self-hosted, desktop, Windows.
- Add open-source tooling advisories to your Incident Escalation triggers, with defined owners and a Notification Timeline for internal stakeholders.
- Align this to your Risk Governance Framework and, where relevant, ISO 27036 supplier relationship controls, so open-source components get the same scrutiny as commercial ones.
Git will have another advisory. The teams that handle it well will be the ones who already know where it runs.





