Patch available CVSS 8.0 Security news
Git 2.56.1 fixes six vulnerabilities: cloning a malicious repository can run attacker code (CVE-2026-111760)
The Git project released version 2.56.1 on 10 November 2026, along with fixes for the 2.50 to 2.55 branches. Six vulnerabilities are fixed. The most serious, CVE-2026-111760, lets an attacker's repository plant its own Git config or hooks during a clone and run code. On 17 November GitHub published details showing this works even without --recurse-submodules. No exploitation has been reported so far. Here is who is affected and what to update.
Key points
- Who is affected: anyone who clones untrusted repositories - developers, security analysts and above all CI/CD pipelines and services that process repositories automatically. Git 2.27.0 and later are affected.
- CVE-2026-111760 (CVSS 8.0): integer truncation in index handling lets an extremely long path pass validation and get written to disk as .git. With a recursive clone the attacker's code runs immediately; with a plain clone it runs after Git suggests running git status.
- Fixed on 10 Nov 2026 in 2.56.1, 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2, together with five other bugs (ref written outside refs/heads, fast-import, GPG signatures, binary patches, merges). Branches older than 2.50 get no fix.
- As of 19 Nov, Debian lists all its releases as vulnerable with no fix. GitHub has patched github.com and GitHub Enterprise Server (3.19.16, 3.20.12, 3.21.10, 3.22.5).
Vulnerabilities: CVE-2026-111760, CVE-2026-113408, CVE-2026-114466, CVE-2026-114467, CVE-2026-114469, CVE-2026-105437
What happened
On 10 November 2026 the Git maintainers released 2.56.1 together with maintenance releases for older branches: 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. Johannes Schindelin announced the release on the oss-security list on 11 November. It fixes six vulnerabilities; according to the announcement every version since 2.27.0 is affected, and branches older than 2.50 are no longer serviced.
The most serious is CVE-2026-111760, rated CVSS 8.0: a repository controlled by an attacker can run code when it is cloned. GitHub, which worked on the fixes, added a technical write-up to its announcement on 17 November. It shows the risk is not limited to cloning with --recurse-submodules, as the original advisory suggested.
In our guide How to safely clone untrusted Git repositories we wrongly stated on 12 November that no fix was available. The guide has been corrected.
Technical details
Before writing files into the working tree, Git checks paths and rejects any that would overwrite its own metadata (the .git directory or file). According to GitHub, the bug comes from integer truncation in index handling: an extremely long path passes validation under one name but is written to disk under a shorter one. That lets an attacker replace .git in the clone and point Git at their own configuration or hooks.
- Recursive clone (
--recurse-submodules): the attacker's code runs during the clone itself. - Plain clone: the top-level
.gitcan point at attacker-controlled metadata. The clone then suggests runninggit status, and anyone who follows that advice runs the code.
The vector AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H reflects that the victim has to clone the attacker's repository themselves. The bug was reported by Robert Chen. We do not publish exploitation details.
The same releases also fix:
| CVE | What it fixes (per the Git maintainers) |
|---|---|
| CVE-2026-113408 | a server can advertise an unborn HEAD in an empty repository (protocol v2) that writes a ref outside refs/heads into the repository root |
| CVE-2026-114466 | fast-import's submodule rewrite features and the export-pack-edges option allowed arbitrary file reads and writes; they are now off by default and need --allow-unsafe-features |
| CVE-2026-114467 | a commit or tag message with more than two GPG signatures overflows a stack array (crash) |
| CVE-2026-114469 | a binary patch that inflates far beyond the roughly 1 GiB limit bypasses the size check and crashes Git |
| CVE-2026-105437 | an integer overflow when sizing merge buffers causes a heap overflow (merge, rebase, cherry-pick, merge-tree) |
Who is affected
- Git 2.27.0 through 2.56.0, except the new maintenance releases.
- Most at risk are CI/CD pipelines and services that automatically clone or process user repositories while holding secrets.
- Apps that bundle Git (IDEs, GitHub Desktop) need their own update. GitHub says GitHub Desktop and the GitHub Copilot app are shipping with the patched Git.
- GitHub Enterprise Server: fixed in 3.19.16, 3.20.12, 3.21.10 and 3.22.5 (these use GitHub-maintained Git builds with different version numbers).
- Linux distributions: as of 19 November, Debian lists bookworm, trixie, forky and sid as vulnerable, with no fix.
How to tell if you were compromised
Neither the Git maintainers nor GitHub have published indicators of compromise, and no exploitation is known. Based on the bug description (this is our inference, not guidance from the maintainers), it is worth checking repositories from untrusted sources that were cloned with an older version:
find . -maxdepth 3 -name .git -type l
git config --show-origin --list | grep -iE "hookspath|fsmonitor|sshcommand"
A symlink in place of .git or unexpected options in the config are reasons to delete the clone and investigate the machine. You can check suspicious links from a repository with our Link checker and break down the score in our CVSS calculator.
What to do
- Check the version (
git --version) on workstations, build agents and container images. - Update to 2.56.1 or the fixed release of your branch. For distribution packages, follow their security notices.
- Until you have updated, do not clone untrusted repositories, merge untrusted tags, or process untrusted binary patches or
fast-importstreams. The maintainers and GitHub stress that this does not replace the fix. - After updating, review your CI: wherever untrusted code is cloned, run it in a disposable environment without tokens (details in our cloning guide).
Timeline
FAQ
Is it enough to avoid --recurse-submodules?
Not entirely. According to GitHub, a plain clone can also be tricked into pointing the top-level .git at attacker-controlled metadata. The clone then suggests running git status, and that runs the attacker's code. Skipping --recurse-submodules lowers the risk but does not replace updating.
I use Git from my Linux distribution. Which version is safe?
Distributions usually backport fixes into packages with older version numbers, so go by their security notices rather than the 2.56.1 number. As of 19 November 2026, Debian had no fixed package in any release.
Does this affect GitHub or GitLab as hosted services?
GitHub says it has deployed fixes on github.com and GitHub Enterprise Cloud and that Codespaces and Actions are getting the patched Git. Self-hosted GitHub Enterprise Server needs updating to 3.19.16, 3.20.12, 3.21.10 or 3.22.5.
Sources
- oss-security - git: v2.56.1 and older maintenance release fixes for six vulnerabilities (Johannes Schindelin, 11 Nov 2026)
- Git - Security advisory GHSA-vp2w-7xxj-jvxr (CVE-2026-111760)
- GitHub Blog - Git security vulnerabilities announced (10 Nov 2026, updated 17 Nov)
- NVD - CVE-2026-111760
- Debian Security Tracker - CVE-2026-111760
Spotted a mistake? Let us know and we will correct it openly.