← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Git Patches Code Execution Flaw in Recursive Clones (CVE-2026-111760)

🔄 Updated 11d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Git fixed CVE-2026-111760 in versions 2.56.1 and earlier series.
  • Flaw allowed code execution via malicious `.git` file in submodules.
  • GitHub has applied fixes to its platforms and is preparing updates.
  • Users should update Git and avoid untrusted recursive clones.

Code Execution Flaw in Git Recursive Clones

A vulnerability, tracked as CVE-2026-111760, has been identified and patched in Git. This flaw allowed an attacker to execute arbitrary code on a user's system when cloning a malicious repository recursively, particularly when submodules were involved. The issue stemmed from an integer truncation error in how Git handled its index, specifically with extremely long paths.

Mechanism of the Attack

The vulnerability exploited Git's handling of long paths. An attacker could craft a repository with an excessively long path that would pass initial safety checks but then be truncated when written to disk. This truncation could rename a file to `.git`, allowing the attacker to replace a submodule's `.git` file (which is typically a file in a fresh clone) with a symbolic link pointing to a directory containing malicious hooks or configuration. Since Git executes hooks at specific points, this enabled code execution.

Patch Availability and Recommendations

The Git project released fixes in Git 2.56.1, along with corresponding updates for older series (2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, and 2.55.1). These patched versions now refuse such long paths before truncation can occur. GitHub has already implemented these fixes on github.com and GitHub Enterprise Cloud, and updates are being prepared for GitHub Enterprise Server, GitHub Desktop, GitHub Copilot, GitHub Codespaces, and GitHub Actions.

Users are strongly advised to update their Git installations from their operating system or Git distributor. Until updates are applied, GitHub recommends cloning only from trusted sources, avoiding recursive clones of untrusted repositories, and not processing untrusted content or binary patches.

Additional Patches

The Git releases also address five other security flaws. These include CVE-2026-113408, which involves a path traversal vulnerability when cloning an empty repository over Git protocol v2, potentially allowing writes outside Git's reference folder. Another fixed flaw, CVE-2026-114467, concerned stack memory corruption when merging a tag with more than two GPG signatures.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Git has released patches for a flaw, CVE-2026-111760, that allowed malicious repositories to execute code during recursive clones by manipulating `.git` files in submodules. The fix prevents extremely long paths from being truncated, which previously enabled attackers to replace `.git` files with symbolic links to malicious hooks. Users are advised to update their Git installations and related tools to the patched versions.