Summary
| Field | Detail |
|---|---|
| Releases | Git 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1, published 2026-11-10 — one per maintained series, each fixing all six CVEs |
| Advisories | Six CVEs, listed under Advisories |
| Headline | CVE-2026-111760 — a recursive clone of a malicious repository can run the attacker’s code: a crafted over-long path lets Git replace a submodule’s .git file with a symbolic link to a directory holding attacker-chosen hooks or configuration |
| Highest severity | CVE-2026-111760: 8.3 high (CVSS 3.1), scored by the Git project’s GitHub advisory; CVE-2026-105437: 7.5 high, scored by GitLab as CNA. The remaining four score lower, also scored by GitLab as CNA: CVE-2026-114469 and CVE-2026-114466 at 4.4 medium, CVE-2026-113408 and CVE-2026-114467 at 3.3 low |
| Types | Code execution through a submodule, a path traversal in ref names, a heap overflow, a stack corruption, an out-of-bounds read, and arbitrary file access through git fast-import |
| Who is exposed | Each bug needs a specific Git operation on attacker-supplied data — see What each bug needs. Code-hosting servers that run merges on behalf of users are exposed to CVE-2026-114467, and to CVE-2026-105437 when they read attributes from the repository’s own trees |
| KEV listed | no |
| Public exploit | CISA’s SSVC assessment scores CVE-2026-105437 Exploitation: PoC — the only one of the six so scored; the other five score none |
Advisories
The Git 2.50.2 release notes describe all six; the other six releases merge that fix up. The GitHub advisory and GitLab’s issues carry the details. CVE-2026-105437 was the first of the six with a published CVE record; GitLab has since published CVE-2026-113408, CVE-2026-114467, CVE-2026-114469, and CVE-2026-114466, and GitHub has now published CVE-2026-111760 as well — all six CVE records are published.
| CVE | Bug | CWE | CVSS 3.1 | Advisory |
|---|---|---|---|---|
| CVE-2026-111760 | Recursive clones are susceptible to remote code execution | CWE-59 | 8.3 | GHSA-vp2w-7xxj-jvxr |
| CVE-2026-105437 | Heap-based buffer overflow when computing a merge buffer | CWE-122 | 7.5 | GitLab #814, GHSA-m7r7-8v36-j77r |
| CVE-2026-113408 | Path traversal through an unborn HEAD a server advertises | CWE-22 | 3.3 | GitLab #809, GHSA-64xm-x3j2-5g2g |
| CVE-2026-114467 | Stack corruption stripping more than two GPG signatures | CWE-787 | 3.3 | GitLab #810, GHSA-mmcj-rqpx-mw52 |
| CVE-2026-114469 | Out-of-bounds read from a binary patch that inflates past the size limit | CWE-125 | 4.4 | GitLab #811, GHSA-g587-3qh4-ghrx |
| CVE-2026-114466 | git fast-import features that read arbitrary paths | CWE-1220 | 4.4 | GitLab #812, GHSA-pppp-mqpq-44j6 |
Not vulnerable: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, 2.56.1, and later releases in each series. Earlier series get no release of their own. The GitHub advisory now gives CVE-2026-111760 explicit affected and patched version ranges, one pair per series, matching the fixed releases above; the release notes give no lower bound for any of the six. CVE-2026-105437’s record lists every release before 2.49.1 as affected, but not 2.49.1 or later 2.49 releases.
Robert Chen reported CVE-2026-111760; Elijah Newren developed the fix with Toon Claes, reviewed by Jeff King and Johannes Schindelin. GitLab credits the HackerOne reporter taise for CVE-2026-105437, and finders ehdgks0627 and un3xploitable for CVE-2026-113408, CVE-2026-114467, CVE-2026-114469, and CVE-2026-114466.
What each bug needs
- CVE-2026-111760 — cloning an attacker’s repository with
--recurse-submodules. The GitHub advisory believes the recursive option is needed. An extremely long path in the repository passes Git’s safety check, but its length is cut short when it is written, so it lands under a name the attacker chose:.git. Git refuses to replace a.gitdirectory with a symbolic link, but in a freshly cloned submodule.gitis a file, and it can be replaced. Git then runs the hooks or reads the configuration in the directory the link points to. - CVE-2026-113408 — cloning an empty repository from a malicious
server over protocol v2. The server advertises an unborn
HEADwhose branch name contains../. With the default files ref backend, a later update to that branch writes outside the repository’s ref directory. - CVE-2026-105437 — a merge with many conflicts and a large
conflict-marker-sizeoverflows the size of the merge buffer, and Git writes past both ends of it. Any textual three-way merge can trigger it —git merge,rebase,cherry-pick,merge-tree— and the attribute can come from a.gitattributesfile committed to the repository. A code-hosting server that runsgit merge-treeto check mergeability, and reads attributes from the repository’s trees (attr.treeor--attr-source), lets anyone who can push a branch and open a merge request trigger it. - CVE-2026-114467 — merging a tag that carries more than two GPG signatures corrupts the stack: a crash, and a denial of service for a hosting service that runs such merges for its users.
- CVE-2026-114469 — applying a binary patch whose compressed form is small but which describes a file over Git’s ~1 GiB patch limit. It slips past the size check and crashes Git with an out-of-bounds read.
- CVE-2026-114466 — running
git fast-importon an untrusted stream.rewrite-submodules-from,rewrite-submodules-to, andexport-pack-edgescould read arbitrary files, or create files and write to them. The fixed releases reject them in an input stream unless--allow-unsafe-featuresis given.
Patch status
A row is Fixed once its Git carries the fix for all six CVEs — the fixed release of its series or any later release, or a distribution package with the patches backported. A package with only some of the fixes stays vulnerable. A vulnerable row that builds an unpatched upstream release names the release it needs: the fixed release of the series it packages.
Current version is what the release ships today; First fixed is the first build that carried the fixes, and Fixed since the date it became available.
| Distribution | Release | Current version | First fixed | Fixed since | Status |
|---|---|---|---|---|---|
| Git | 2.56 series | 2.56.1 | 2.56.1 | 2026-11-10 | ✅ Fixed |
| Git | 2.55 series | 2.55.1 | 2.55.1 | 2026-11-10 | ✅ Fixed |
| Git | 2.54 series | 2.54.1 | 2.54.1 | 2026-11-10 | ✅ Fixed |
| Git | 2.53 series | 2.53.1 | 2.53.1 | 2026-11-10 | ✅ Fixed |
| Git | 2.52 series | 2.52.1 | 2.52.1 | 2026-11-10 | ✅ Fixed |
| Git | 2.51 series | 2.51.3 | 2.51.3 | 2026-11-10 | ✅ Fixed |
| Git | 2.50 series | 2.50.2 | 2.50.2 | 2026-11-10 | ✅ Fixed |
| Debian | sid (unstable) | 1:2.55.0-1 | — | — | ❌ Vulnerable |
| Debian | forky (testing) | 1:2.53.0-1 | — | — | ❌ Vulnerable |
| Debian | 13 (trixie) | 1:2.47.3-0+deb13u1 | — | — | ❌ Vulnerable |
| Debian | 12 (bookworm) | 1:2.39.5-0+deb12u3 | — | — | ❌ Vulnerable |
| pkgsrc | pkgsrc-current — devel/git-base | git-base-2.56.1nb1 | git-base-2.56.1 | 2026-11-10 | ✅ Fixed |
| pkgsrc | pkgsrc-2026Q3 — devel/git-base | git-base-2.55.0nb1 | — | — | ❌ Vulnerable — needs 2.55.1 |
| NixOS | nixos-unstable | 2.56.0 | — | — | ❌ Vulnerable — needs 2.56.1 |
| NixOS | nixos-unstable-small | 2.56.0 | — | — | ❌ Vulnerable — needs 2.56.1 |
| NixOS | nixos-26.05 | 2.54.0 | — | — | ❌ Vulnerable — needs 2.54.1 |
| NixOS | nixos-26.05-small | 2.54.0 | — | — | ❌ Vulnerable — needs 2.54.1 |
| nixpkgs | master branch | 2.56.0 | — | — | ❌ Vulnerable — needs 2.56.1 |
| nixpkgs | release-26.05 branch | 2.54.0 | — | — | ❌ Vulnerable — needs 2.54.1 |
| nixpkgs | nixpkgs-unstable | 2.56.0 | — | — | ❌ Vulnerable — needs 2.56.1; channel for non-NixOS Nix users |
Git
Git fixed every series from 2.50 onwards in one coordinated release, and any of the seven fixed releases is safe. A host on a series older than 2.50 gets no upstream release: it has to move to a fixed series, or rely on its distribution’s backports.
GitHub has applied the fixes to github.com and GitHub Enterprise Cloud. Git for Windows, GitHub Desktop, and other applications that bundle their own copy of Git need their own updates.
Debian
The Debian security tracker is the authoritative source for per-suite status; it carries a page per CVE. All four suites ship a Git from before the fixed releases, so each needs either a new upstream release or a backport of all six fixes. trixie and bookworm ship series older than 2.50, which only a security upload with backported patches can fix.
pkgsrc
The pkgsrc tree (NetBSD’s package collection, also used on SmartOS,
macOS via pkgin, and elsewhere) builds the Git commands from
devel/git-base; devel/git is the meta-package that pulls it in.
pkgsrc-2026Q3, the current quarterly branch, receives fixes by
pull-up from pkgsrc-current.
The identifier carries an nbN suffix when the package’s
PKGREVISION is set. That revision bumps for many reasons besides
security patches — recursive bumps for shared-library ABI changes,
dependency and build-system tweaks — so an nbN suffix on its own
says nothing about these CVEs.
NixOS
nixpkgs builds Git from a single expression,
pkgs/by-name/gi/git/package.nix; the git, gitFull,
gitMinimal, and gitSVN attributes are all built from it, so one row
per channel covers every variant.
Git is a mass-rebuild package in nixpkgs: an update to it lands on the
staging branch first and reaches master, and then the channels, only
with the next staging cycle.
nixpkgs-unstable is the channel for Nix users outside NixOS — on
macOS or another Linux distribution. A channel row’s Fixed since is
the date that channel published its first release containing the fix;
a branch row’s is the date the fix was merged into that branch.
Flake users
A flake input such as github:NixOS/nixpkgs/nixos-unstable follows
the branch of that name, which moves with the channel — so the
channel’s row answers for it. An input on master or release-26.05
gets the fix as soon as it lands there, before any channel publishes
it.
Detection
Check the version. A release at or past its series’ fixed release is fixed; a distribution build is fixed only once the table above says so.
git --version
Distribution packages keep the upstream version and bump their own revision for a backport. The installed package version is what to compare against the table — on Debian:
dpkg-query -W -f='${Version}\n' git
On pkgsrc, where the identifier is git-base-<version> plus an
nb<PKGREVISION> suffix when one is set:
pkg_info -e git-base
On NixOS, git --version above reports the version built into the
profile or system closure; compare it with the channel’s row.
CVE-2026-111760 needs a clone with --recurse-submodules;
submodule.recurse does not make git clone recursive.
A server reaches CVE-2026-105437 through merge checks only when it
reads attributes from the repository’s trees. attr.tree set in the
server’s Git configuration is one way; --attr-source passed by the
forge’s own merge-check command is the other, and only the forge’s
configuration shows that:
git config --get attr.tree
Mitigation
The real fix is a fixed Git release, or a distribution package with the patches. Until one is installed, GitHub’s advice, which does not replace the fixes:
- Clone only from servers you trust.
- Do not recursively clone repositories you do not trust.
- Do not merge content or tags you do not trust.
- Do not apply binary patches or run
git fast-importon streams from sources you do not trust.
For CVE-2026-105437, GitLab suggests that a server that cannot upgrade
yet set conflict-marker-size=7 for every path in each repository’s
info/attributes file, which overrides any committed attribute — or
turn off merge checks for untrusted repositories. Run these inside
each repository; the first creates info/ where it is missing:
mkdir -p "$(git rev-parse --git-path info)"
printf '* conflict-marker-size=7\n' >> "$(git rev-parse --git-path info/attributes)"
A configuration change does not change a row’s status above: only a Git build with the fixes does.
Verification log
Every verdict in the table above is backed by a checkable source. This log records the provenance — the advisory, repository index, or git reference that established each fact — so any row can be audited or reproduced. Most readers never need it.
Full verification log
Upstream
- Git release notes (
Documentation/RelNotes/<version>.adocin the git repository):- 2.50.2’s notes describe all six; 2.51.3 through 2.56.1 each merge up the fix from the earlier releases and refer to their notes.
- 2.50.2’s notes link GHSA-vp2w-7xxj-jvxr for CVE-2026-111760 and GitLab issues #809–#812 and #814 for the others, and list “reject cache entries with over-long names” as a separate defense-in-depth fix.
- Git tags (local clone of
git.kernel.org/pub/scm/git/git.git):- The seven release commits are dated 2026-10-23; the tags were signed during the embargo, 2.56.1 on 2026-10-26 and the other six on 2026-11-03.
- The six maint tags’ messages all read “Git 2.50.2”.
- Current version is the newest tag in each series.
- Release tarballs (kernel.org):
- All seven
git-<version>.tar.xzfiles are dated 2026-11-10, the upstream rows’ Fixed since.
- All seven
- Fix commits (the 2.50.2 series, local clone):
- CVE-2026-111760:
29411cf59f(“read-cache: reject cache entries with over-long names”) describes the exploit — a.gitz/z…z/zpath written as.git— and carries Robert Chen’s Reported-by, though the release notes file it as defense-in-depth. fd48e6f356anddf24683924harden related cache entry length computations incheckoutandread-cachewithsize_tand overflow checks.- CVE-2026-113408:
b371db8125,8cb7e2e031, andf357b9c2c7validate symref targets and ref names in protocol v2 responses. - CVE-2026-105437:
288266c11dandb1313872cecompute the merge buffer size inxdiffassize_twith overflow checks, using thest_add5()helper0dc3b5c022adds. - CVE-2026-114467:
aff5872223rewritesremove_signature()to handle any number of signatures. - CVE-2026-114469:
55c54fd375rejects binary patches larger thanMAX_APPLY_SIZE. - CVE-2026-114466:
2b50a97225and19bcf62ed0guard therewrite-submodulesfeatures andexport-pack-edges.
- CVE-2026-111760:
- GitHub advisory (the Git project’s repository advisory
API):
- GHSA-vp2w-7xxj-jvxr published 2026-11-10, revised 2026-11-17 to
CVSS 3.1
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H(8.3), no CWE. - Its affected and patched version fields now list each series' pre-fix range and its fixed release, in place of the earlier “all”/“none”.
- It believes the bug “can only be triggered when the
--recurse-submodulesoption is used”.
- GHSA-vp2w-7xxj-jvxr published 2026-11-10, revised 2026-11-17 to
CVSS 3.1
- CVE records (the CVE Services API):
- CVE-2026-105437 published 2026-11-10 by GitLab: CVSS 3.1
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H(7.5), CWE-122, credited to taise via HackerOne. - Its affected ranges are
0to before 2.49.1, then each series from 2.50 to 2.56 before its fixed release, with every other version unaffected. - Its description limits the forge scenario to servers reading
attributes from trees, through
attr.treeor--attr-source. - CISA ADP’s SSVC assessment for CVE-2026-105437, dated 2026-11-16: exploitation proof-of-concept, not automatable, total technical impact.
- CVE-2026-113408 published 2026-11-12 by GitLab: CVSS 3.1
AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N(3.3), CWE-22. - CVE-2026-114467 published 2026-11-12 by GitLab: CVSS 3.1
AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L(3.3), CWE-787. - CVE-2026-114469 published 2026-11-12 by GitLab: CVSS 3.1
AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L(4.4), CWE-125. - CVE-2026-114466 published 2026-11-12 by GitLab: CVSS 3.1
AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N(4.4), CWE-1220. - CISA ADP’s SSVC assessment for CVE-2026-113408, CVE-2026-114467, CVE-2026-114469, and CVE-2026-114466, dated 2026-11-17: exploitation none, not automatable, partial technical impact for each.
- CVE-2026-111760 published 2026-11-16 by GitHub: CVSS 3.1
AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H(8.0), CWE-59 — unchanged since the GitHub advisory’s own CVSS was later revised to 8.3. - Its affected ranges carry no lower bound, unlike the version ranges the GitHub advisory now gives.
- CISA ADP’s SSVC assessment for CVE-2026-111760: exploitation none, not automatable, total technical impact.
- CVE-2026-105437 published 2026-11-10 by GitLab: CVSS 3.1
- NVD (the NVD 2.0 API):
- All six CVEs are now in NVD, each matching its CNA score; no CISA KEV entry for any of the six.
- GitHub advisory database (
api.github.com/advisories, by CVE id):- GHSA-m7r7-8v36-j77r for CVE-2026-105437, GHSA-64xm-x3j2-5g2g for CVE-2026-113408, GHSA-mmcj-rqpx-mw52 for CVE-2026-114467, GHSA-g587-3qh4-ghrx for CVE-2026-114469, and GHSA-pppp-mqpq-44j6 for CVE-2026-114466; none for CVE-2026-111760.
- The Hacker News (2026-11-10 report):
- The source for the CVE-2026-111760 mechanism, GitHub’s interim
advice, and GitLab’s
merge-treescenario and workaround.
- The source for the CVE-2026-111760 mechanism, GitHub’s interim
advice, and GitLab’s
Distributions
- Debian (security tracker per-CVE pages; Current version from
scripts/debian-versions):- All six pages list sid, forky, trixie, and bookworm as open, with no fixed version.
- No changelog in any suite names a tracked CVE.
- pkgsrc (local clone,
scripts/pkgsrc-versions):devel/git-baseonorigin/trunkandorigin/pkgsrc-2026Q3; its version isGIT_VERSIONindevel/git/Makefile.version. No patch names a tracked CVE.origin/trunk’sGIT_VERSIONreached2.56.1in commit30957b46fd6e, dated 2026-11-10 —pkgsrc-current’s Fixed since.
- NixOS channels (local nixpkgs clone at each channel’s revision,
scripts/nixpkgs-versions):- Versions read from
pkgs/by-name/gi/git/package.nix; no file underpkgs/by-name/gi/gitnames a tracked CVE.
- Versions read from
- nixpkgs branches (local clone):
- The
git: 2.56.0 -> 2.56.1update (#586339) reachedstagingon 2026-11-10.
- The
- NixOS security tracker (tracker.security.nixos.org) — a JS-rendered application; linked for readers, not read by this tracker.