Threat Intelligence

Git Update Fixes Flaw That Lets Booby-Trapped Repositories Run Attacker Code

The Hacker News · 11 Nov 2026
Key Takeaway Update Git on developer machines and servers to a fixed version as soon as it is available, and be cautious about recursively cloning repositories you do not trust.

The Git project has fixed a flaw that can let a malicious repository run an attacker's code on a computer that clones it recursively, meaning together with its submodules. The fix arrived this week in Git 2.56.1, with matching fixes for the 2.50 through 2.55 series in versions 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1 and 2.55.1. The flaw is tracked as CVE-2026-111760.

The problem is an integer truncation in how Git handles its index. An extremely long path can pass Git's safety check, but Git then writes it to disk under a shorter name that an attacker can set to .git. That lets an attacker swap a submodule's .git file for a symbolic link to a folder holding malicious hooks or configuration. Hooks are programs Git runs at set points, so once Git uses that folder, the attacker's code can run. The fixed versions refuse such extremely long paths before their length can be cut short.

GitHub advises installing a fixed version from your operating system or Git distributor, and updating any app that ships its own copy of Git. It has already applied the fixes to github.com and GitHub Enterprise Cloud. Fixed versions of GitHub Desktop and the GitHub Copilot app are being prepared. As of Tuesday at 19:09 UTC, Git for Windows had not released a version based on Git 2.56.1, according to The Hacker News. The Git releases also fix five other flaws, and GitLab said code-hosting servers are most likely to be targeted through git merge-tree.

Git CVE-2026-111760 Software Supply Chain Patching
Answering to more than one framework? Run them as one security and AI governance programme ->

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.