CVE Tools

Git fixes six vulnerabilities, including code execution during recursive clones

Help Net SecurityBy Anamarija Pogorelec

Our summary

The Git project shipped security fixes for six vulnerabilities that could let attackers run arbitrary code, write files outside intended locations, or crash and corrupt memory when Git handles malicious repositories, patches, or import streams. The most severe, CVE-2026-111760, exploits an integer truncation in index-path handling, letting a long file path bypass checks and then get written under a shortened name — allowing a submodule's .git file to be swapped for a symlink that triggers attacker code during a recursive clone. CVE-2026-113408 lets a malicious server abuse an unvalidated HEAD reference during a protocol v2 clone of an empty repo to write outside the reference directory, while CVE-2026-114467 (GPG signature stripping), CVE-2026-114469 (oversized binary patches), CVE-2026-105437 (merge buffer overflow), and CVE-2026-114466 (unsafe git fast-import options) can cause crashes, memory corruption, or information leaks. The fixes are included in Git 2.56.1, with backports for the 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, and 2.50.2 branches, and GitHub has already deployed protections on github.com and its Enterprise Cloud offerings while urging Enterprise Server admins to upgrade to 3.19.15, 3.20.11, 3.21.9, or 3.22.4. Users and administrators who can't update immediately are advised to avoid recursive clones and merges of untrusted repositories as a temporary mitigation.

Read at Help Net Security

Help Net Security publishes this story on its own site; we link to it rather than reprint it.

Worried this affects your company?

Discuss a security assessment of your internet-facing systems. Scope agreed before testing.

Check my exposure