Git Recursive Clone RCE: Find the Clones You Didn't Type
On November 10, 2026 the Git project shipped fixes for six vulnerabilities, and the one that matters most is a recursive clone vulnerability: a crafted repository can run code on your machine when you clone it with its submodules. You may never type git clone --recurse-submodules yourself, but pip and npm can run the equivalent submodule update on your behalf, and so can actions/checkout if you ask it to. Check your Git against the fixed versions below, then grep your repositories for those clones.
1. What Git 2.56.1 Fixes and Which Versions Have It
The GitHub Blog announcement and the Git release notes list six CVEs. CVE-2026-111760 is the remote code execution (RCE) bug. An integer truncation in Git's index handling lets an extremely long path pass validation under one name and get written under a shorter one. An attacker uses that to replace a submodule's .git file with a symbolic link to a directory holding malicious config or hooks, which Git then runs during the recursive clone. The details are in GHSA-vp2w-7xxj-jvxr.
The other five are narrower. A malicious server can advertise an unborn HEAD with path-traversal characters when you clone an empty repository over protocol v2, and later ref updates write outside the refs directory. Merging a tag with more than two GPG signatures corrupts the stack. Binary patches that inflate past the roughly 1 GiB limit cause an out-of-bounds read, very large merges (many conflicts combined with a big conflict-marker-size) corrupt the heap, and three git fast-import options could read or write files outside the repository. The HEAD bug hits clients that use the files ref backend. The merge, patch and fast-import bugs mostly matter to services that process untrusted content, though the merge overflow also affects local merges.
Fixed versions: 2.56.1, 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2. The announcement lists no backport for series older than 2.50. GitHub's advice if you cannot update yet: clone only from trusted servers and avoid recursive clones of untrusted repositories.
2. On Linux, the Version Number Does Not Show the Fix
For a Git you built yourself, or one from Git for Windows, the number from git --version is enough. This script compares it with the fixed release of its series and exits non-zero when something is missing, so it can run as a CI step. We tested it with bash 5 against a dozen version strings, including 2.56.1.windows.1.
#!/usr/bin/env bash
# check-git.sh: is this Git at or above the Nov 10, 2026 fix for its series?
v=$(git --version | awk '{print $3}')
IFS=. read -r major minor patch _ <<< "$v"
case "$major.$minor" in
2.5[2-6]) need=1 ;;
2.51) need=3 ;;
2.50) need=2 ;;
*) if [ "$major" -gt 2 ] || { [ "$major" -eq 2 ] && [ "$minor" -gt 56 ]; }; then
echo "git $v: newer series than 2.56"; exit 0
fi
echo "git $v: no upstream fix for this series, ask your distro"; exit 2 ;;
esac
patch=${patch%%[!0-9]*} # 0-rc1 -> 0
if [ "${patch:-0}" -ge "$need" ]; then
echo "git $v: patched"
else
echo "git $v: missing the fix, need $major.$minor.$need"; exit 1
fiExit code 2 means the announcement lists no fix for that series. On Ubuntu 24.04, git --version reports 2.43.0. Distributions often backport security patches into the version they froze, so for a packaged Git the full package version is what counts:
$ git --version
git version 2.43.0
$ dpkg-query -W -f='${Version}\n' git
1:2.43.0-1ubuntu7.4The Debian security tracker tracks versions this way, by full package version such as 1:2.39.5-0+deb12u3 for bookworm. On November 12, 2026 it listed bookworm (2.39.5), trixie (2.47.3) and even sid (2.55.0) as still vulnerable, with no fixed package yet. When Debian ships a fix for bookworm, Git will keep reporting 2.39.5 and only the revision after the hyphen will change. That is why the script stops at "ask your distro" and leaves the answer to your distribution's tracker.
3. pip, npm and actions/checkout Can Update Submodules for You
A recursive clone is not only the --recurse-submodules flag. The git clone documentation says that flag is equivalent to running git submodule update --init --recursive right after the clone. Several tools run exactly that.
pip installs from git URLs
A requirement like mytool @ git+https://... makes pip clone the repository. After checkout, pip's git backend calls git submodule update --init --recursive whenever a .gitmodules file exists. We read it in the pip 24.0 that ships with Ubuntu 24.04 and in pip 26.3's vcs/git.py: both do it.
npm, when it has to clone
npm's @npmcli/git clone.js passes --recurse-submodules when it clones a branch or the default HEAD, and runs the recursive submodule update when it checks out a specific commit. The version bundled with npm 10.9.9 (6.0.3) has the same code. npm is less exposed than pip, though: for dependencies on hosts it knows how to download archives from (GitHub, GitLab and Bitbucket among them), pacote's git fetcher first downloads a tarball of the commit, and tarballs have no submodules. It falls back to a real clone when that download fails with an HTTP error, which is what happens with a private repository, and git URLs on other hosts are cloned directly.
actions/checkout with submodules turned on
In actions/checkout the submodules input defaults to false. With recursive, the action's git command manager runs git submodule update --init --force --recursive, which Git documents as what a recursive clone does after cloning. With true it runs that command without --recursive, so only the first level of submodules is fetched; the advisory does not say whether that path is exploitable.
These two greps, run from the root of a repository, catch the common cases. The lockfile matters: a git dependency pulled in by another package shows up only there.
# git dependencies, direct and transitive grep -rnE '"(github:|gitlab:|bitbucket:|git\+|git://)|git\+(https|ssh)://' \ --exclude-dir=node_modules --include='package*.json' \ --include='requirements*.txt' --include=pyproject.toml . | grep -v '"url"' # workflows that check out submodules grep -rnE "submodules:[[:space:]]*[\"']?(true|recursive)" .github/workflows/
Setting submodule.recurse=true in your Git config does not make git clone recursive. The git-config reference lists clone among the commands the setting does not apply to.
The greps are not exhaustive. They miss npm's bare owner/repo shorthand, plain https://...git URLs and other lockfiles (yarn.lock, pnpm-lock.yaml, poetry.lock, uv.lock). And the advisory only talks about recursive clones: for pip, npm's commit checkouts and actions/checkout this article relies on Git's own statement that the flag and the submodule update are the same operation. A hit that points to a repository you control is lower risk, not zero, because its submodules can point somewhere else. A hit that points to a stranger's repository means running that install only with a patched Git (2.56.1 or the fix for your series), or holding it until your distribution ships one.
4. The Fix Reaches Each Copy of Git on a Different Day
A developer machine often has two or three Git binaries, and each one updates through its own channel. Here is where things stood on November 12, two days after the release:
- Git for Windows 2.56.1 came out on November 10 and is marked Latest.
- GitHub Desktop updated its embedded Git to 2.56.1 in 3.6.12-beta1, a pre-release from November 11. The release marked Latest, 3.6.10, predates the fix.
- The ubuntu-24.04 runner image README listed Git 2.56.0 for image version 20261101.360.1. GitHub says Actions and Codespaces will receive patched versions, without a date.
- GitHub Enterprise Server has fixes in 3.19.15, 3.20.11, 3.21.9 and 3.22.4, according to the same announcement, and github.com itself is already patched.
Docker images that install Git from Debian's packages inherit that package, so they wait for the tracker entry above to show a fixed version and for the image to be rebuilt. Editors and GUI clients may bundle their own copy too. Running type -a git lists every git on your PATH, but not the ones an application keeps inside its own install directory, so check those apps' release notes for an embedded Git update.
5. git/git Has No GitHub Releases to Watch
git/git cannot be followed through GitHub Releases. The git/git releases page says "There aren't any releases here": the project publishes tags (v2.56.1, v2.51.3 and so on) but no GitHub Releases. Our post on GitHub releases vs tags covers why that difference matters for anything that watches releases. GitWatchman is one of those tools: it refuses repositories with no releases, so it cannot follow git/git.
What works instead depends on which Git you run. Windows users can follow git-for-windows/git, whose 2.56.1 release names the CVEs in its notes. The GitHub Blog Git tag feed carried this announcement and works in any feed reader. On Linux, the patched package version appears first in your distribution's own channel, such as Debian security advisories or Ubuntu Security Notices.
GitHub Desktop shows a second limit. GitWatchman notifies the release GitHub marks as Latest, which excludes pre-releases, so following desktop/desktop would have told you nothing on November 11: the patched Git is only in a beta. If you want betas too, a feed of all releases is the better tool, as explained in our guide to tracking pre-releases.
Frequently Asked Questions
Which Git versions fix CVE-2026-111760?
Git 2.56.1, 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2, all released on November 10, 2026. The announcement lists no upstream backport for older series. Distributions such as Debian ship older series and patch their own packages, so for a distro Git the answer is in the distribution's security tracker, not in the upstream version number.
Does npm install clone git dependencies with submodules?
Sometimes. When npm (we read 10.9.9) has to clone a git dependency, its @npmcli/git module runs git clone with --recurse-submodules, or git submodule update --init --recursive. For GitHub, GitLab, Bitbucket and a few other known hosts npm first tries a tarball download, which has no submodules, and clones only if that download fails, as it does for a private repository. Git URLs on other hosts are cloned.
Is GitHub Actions exposed to CVE-2026-111760?
GitHub has not said. Its announcement says Actions and Codespaces will receive a patched Git, without a date. A job matches the advisory's scenario only if a step clones or updates untrusted submodules recursively, for example actions/checkout with submodules: recursive. On November 12, 2026 the ubuntu-24.04 runner image README still listed Git 2.56.0. A step that runs git --version tells you what your job actually got.
Can I get notified of new Git releases on GitHub?
Not from git/git: the repository publishes tags but no GitHub Releases, so release monitors that read Releases, GitWatchman included, cannot follow it. Git for Windows does publish releases (2.56.1 is marked Latest), and the GitHub Blog has a Git tag feed that carried the November 10 security announcement.
Know the day Git for Windows ships its next fix
Follow git-for-windows/git and up to four more GitHub repositories, free during the beta. GitWatchman checks for new releases every two hours and sends them by email, Slack, Discord or Telegram, or to your personal RSS feed.
Start tracking for free