Ubiquitous code repository project Git patches two flaws, including one letting an attacker execute code on systems that recursively cloned a malicious Git repo
Catalin Cimpanu / BleepingComputer.com :
Context & Ripple Effects
Git's clone operation has been an attack surface before: a 2014 flaw in Git and Mercurial allowed arbitrary code execution on OSX and Windows through Visual Studio and the GitHub desktop client. The new patch extends that pattern to recursive clones specifically — the default behavior of tools and scripts that pull a repo together with its submodules.
The timing lands amid a documented wave of repository abuse: researchers have detailed [[a:849868|repo confusion attacks infecting cloned repos with malware loaders across 100K+ GitHub repositories]], and Recorded Future has catalogued how criminals and APTs use GitHub for malware delivery. A code-execution bug in the clone path turns that delivery channel into a direct compromise vector.
First-order effects
- Developers, CI pipelines, and any automation running recursive clones must update Git immediately, since a single `git clone --recursive` of a crafted repo executes attacker code before any review happens.
- Downstream packagers — Linux distributions, IDE vendors, hosted runners — inherit the fix and face the same forced-update cycle the 2014 Git/Mercurial flaw imposed on Visual Studio and the GitHub client.
Second-order effects
- Hosting platforms and CI providers that clone untrusted repos at scale absorb the operational cost, echoing GitHub's scramble after its npm authentication-bypass flaws showed how compromise of the distribution layer propagates to every consumer.
- Security teams tighten policy around submodule fetching and pinned dependencies, shifting recursive clone from a convenience default to a flagged action in hardened environments.
Third-order effects
- Version-control clients are being treated like package managers — critical supply-chain infrastructure whose client-side bugs are disclosure-worthy and patched on emergency cadence, aided by channels such as GitHub's private vulnerability reporting reaching general availability.
- If clone-path exploits keep recurring alongside repo confusion campaigns, expect sandboxed or credential-stripped defaults for recursive operations to become standard rather than opt-in hardening.
The trend: The software supply chain's attack surface is moving upstream from published packages to the version-control tooling itself, making clone and fetch operations a recurring code-execution frontier.