← All security news
SecurityPatchHIGH

Update Git: 2.56.1 fixes six flaws, including CVE-2026-111760, which lets a malicious repository run code when you clone it with submodules

· 1 min read

Git 2.56.1 and backports for 2.50–2.55 fix six vulnerabilities released on 10 November 2026. The worst can run attacker code during a recursive clone. GitHub.com is patched; Enterprise Server needs an upgrade. No exploitation is reported.

Git

The Git project released Git 2.56.1 on 10 November 2026 to fix six security vulnerabilities, with backports in 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. GitHub says the fixes are already deployed on github.com and GitHub Enterprise Cloud, and that GitHub Desktop, the GitHub Copilot app, Codespaces and Actions are getting the patched Git. GitHub Enterprise Server admins should upgrade to 3.19.15, 3.20.11, 3.21.9 or 3.22.4.

The most serious bug, CVE-2026-111760 (CVSS 8.0 according to SecurityOnline), is in index handling: an overlong path passes validation under one name and is written under a shorter one. An attacker can use this to replace a submodule's .git file with a symlink to a directory holding malicious config or hooks, so code can run during a recursive clone (git clone --recurse-submodules).

The other five:

  • CVE-2026-113408: when you clone an empty repository over protocol v2, a malicious server can send a HEAD target with path-traversal parts and make Git write outside the refs directory.
  • CVE-2026-114467: merging a tag with more than two GPG signatures can corrupt the stack; hosting services that merge for users are affected too.
  • CVE-2026-105437: a size overflow in very large merges with many conflicts can corrupt the heap (CVSS 7.5 per SecurityOnline).
  • CVE-2026-114469: a small compressed binary patch can expand past Git's ~1 GiB limit and crash Git.
  • CVE-2026-114466: three git fast-import features could read or write arbitrary files from an untrusted stream; they are now refused unless you pass --allow-unsafe-features.

No exploitation in the wild and no public exploit code have been reported. The advisories do not name who found the bugs.

More news