← All security briefings

Attention

Git: cloning a malicious repository can run attacker code, including non-recursive clones

Identifiers: CVE-2026-111760 · GHSA-vp2w-7xxj-jvxr

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

CVE-2026-111760 (GHSA-vp2w-7xxj-jvxr) is an integer truncation bug in Git's index handling. An attacker-controlled server can supply trees whose combined path lengths overflow the cache-entry name-length field, letting checkout overwrite .git despite path validation and redirect Git to attacker-controlled configuration or hooks. The Git project advisory, updated 17 November 2026 20:45 UTC, now states exploitation is not limited to recursive clones. In a recursive clone, code can run during the clone itself. In a non-recursive clone, the top-level .git directory can be replaced by a gitfile pointing to attacker-supplied metadata; the clone can then fail and suggest running git status, and following that suggestion can execute attacker code through core.fsmonitor. The advisory now lists concrete affected and patched ranges, replacing the placeholder metadata noted in our 11 November briefing.

Classification reason: Corrected 18 November 2026: the project advisory updated 17 November 2026 expands scope to non-recursive clones and now lists concrete affected and patched versions; GitHub's post, originally published 10 November 2026 and updated 17 November 2026, adds Enterprise Server targets. Ubuntu's tracker still shows 'Needs evaluation'. No observed exploitation is established by the reviewed sources.

Impact

Arbitrary code runs with the privileges of the user or service that performs the clone or follows Git's post-failure suggestion. Developer workstations, CI runners, build agents and applications that bundle Git are the practical targets.

Who is affected

Affected per the project advisory: Git 2.50.1 and earlier, 2.51.0 to 2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0 and 2.56.0. Fixed in 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1 and 2.56.1, or a distributor security backport. GitHub's server-side fixes do not patch local Git, bundled clients or CI images. At the time of this review, Ubuntu's tracker shows 'Needs evaluation' for every listed release, including Noble and Jammy; this means a fixed Ubuntu package revision has not yet been verified in this review, not that one will not be issued. Once Canonical publishes a security notice, that notice takes precedence over any raw upstream version comparison. GitHub Enterprise Server administrators should use 3.19.16, 3.20.12, 3.21.10 or 3.22.5, whose bundled Git version numbers differ from the upstream releases above.

Products and versions

Products and versionsAffectedFixed
Git <= 2.50.1, 2.51.0-2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0, 2.56.0 2.56.1; 2.55.1; 2.54.1; 2.53.1; 2.52.1; 2.51.3; 2.50.2, or distributor backport

Exploitation evidence

Exploitation not established. As of 18 November 2026, neither the Git project advisory nor GitHub's updated post reports observed exploitation; no observed exploitation is established by the reviewed sources.

Sources: Git project, GitHub

Actions

  1. Update every Git binary to 2.56.1 or the matching maintenance release (2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, 2.50.2), or your distributor's security backport.
  2. Rebuild CI runner images, containers and applications that bundle their own Git.
  3. Confirm the binary actually invoked on each PATH is a fixed release or backport revision, not just a version banner.
  4. Until updated, avoid cloning repositories from untrusted sources entirely; omitting --recurse-submodules is not a sufficient mitigation.
  5. If a clone from an untrusted source fails, do not run git status or any other Git command inside the resulting directory. Stop using that checkout and ask your administrator or security team to isolate and preserve it for review without using Git.
  6. GitHub Enterprise Server administrators: upgrade to 3.19.16, 3.20.12, 3.21.10 or 3.22.5.

Unknowns

  • Ubuntu's tracker shows 'Needs evaluation' for Noble, Jammy and other listed releases at the time of this review; a fixed Ubuntu package revision has not yet been verified here.
  • Distributor-specific backport versions for other platforms are not listed here; confirm with your distributor.

Sources

  • Git project · published · updated · retrieved https://github.com/git/git/security/advisories/GHSA-vp2w-7xxj-jvxr
  • Git project · retrieved https://github.com/git/git/blob/v2.56.1/Documentation/RelNotes/2.56.1.adoc
  • GitHub · retrieved https://github.blog/open-source/git/git-security-vulnerabilities-announced-7/
  • Canonical Ubuntu · retrieved https://ubuntu.com/security/CVE-2026-111760

Change history

  1. — Published: 11 November 2026: ViWeb published this briefing based on sources dated 10 November 2026: the Git project advisory GHSA-vp2w-7xxj-jvxr (CVE-2026-111760), last updated 10 November 2026 19:09 UTC and still showing placeholder metadata; the Git 2.56.1 release notes stating the fix is merged and also present in 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1 and 2.55.1; and GitHub's corroborating release post of the same day.
  2. — Correction: 18 November 2026: ViWeb issued a material correction. The Git project advisory GHSA-vp2w-7xxj-jvxr (CVE-2026-111760), updated 17 November 2026 20:45 UTC, now states exploitation is not limited to recursive clones: a non-recursive clone can replace the top-level .git with a gitfile, and running the git status command Git suggests after the failed clone can execute attacker code. Our 11 November briefing described the issue as recursive-only and advised avoiding recursive clones of untrusted repositories as an interim measure that was not a guaranteed fix; that narrowing to recursive clones is withdrawn, and the interim guidance is now to avoid all clones of untrusted repositories until patched. The advisory also replaced its placeholder metadata with concrete affected ranges (2.50.1 and earlier, 2.51.0-2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0, 2.56.0) and patched versions, so the earlier note about stale metadata is removed. GitHub's post, originally published 10 November 2026 and updated 17 November 2026, adds Enterprise Server targets 3.19.16, 3.20.12, 3.21.10 and 3.22.5. Ubuntu's tracker shows 'Needs evaluation' for Noble, Jammy and other listed releases at the time of this review.

Subscribe: RSS feed · JSON Feed · Feed format and fields