cve.bz

CVE-2026-111760 Git: Recursive clones are susceptible to Remote Code Execution

8.0 highEPSS 0.7%

High (8.0) in git git. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Prior to 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1, an attacker-controlled repository hosted by the attacker rather than on a normal forge site can exploit git clone --recurse-submodules by causing Git to overwrite a submodule gitfile with a symbolic link. The symbolic link can point to a directory containing attacker-controlled Git configuration or hooks, allowing those hooks or configuration to execute code on the cloning user's system. The issue requires the recursive-submodule option, and users should avoid cloning repositories from untrusted sources. This issue is fixed in versions 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS
0.7% estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-111760 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111760?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111760?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111760 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
git< 2.50.2
git>= 2.51.0, < 2.51.3
git>= 2.52.0, < 2.52.1
git>= 2.53.0, < 2.53.1
git>= 2.54.0, < 2.54.1
git>= 2.55.0, < 2.55.1
git>= 2.56.0, < 2.56.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14gitno fix listedDEBIAN-CVE-2026-111760
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moregitno fix listedUBUNTU-CVE-2026-111760
openSUSETumbleweedgit2.56.1-1.1openSUSE-SU-2026:12538-1
Alpinev3.23git2.52.1-r0ALPINE-CVE-2026-111760
Alpinev3.24git2.54.1-r0ALPINE-CVE-2026-111760
Azure Linux3gitno fix listedAZL-114293
Alpaquita23git2.43.7-r1BELL-CVE-2026-111760
Alpaquita25git2.50.2-r0BELL-CVE-2026-111760
Alpaquitastreamgit2.56.1-r0BELL-CVE-2026-111760

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important rather than Critical because exploitation requires a specific precondition where a user or automated pipeline initiates a recursive repository retrieval against an untrusted source. In typical Red Hat environments, Git is frequently deployed within CI/CD pipelines and developer workstations, exposing those environments to arbitrary code execution if third-party repositories are processed without verification. Although the blast radius is bounded by the privileges of the executing account, such exploitation could compromise build environments or access tokens.

Red Hat's mitigation

Avoid performing recursive repository retrieval operations on untrusted sources.

Operational controls:

1. Do not use the `--recurse-submodules` or `--recursive` flags when executing `git clone` on untrusted or external repositories.

2. If submodules are required, clone repositories non-recursively and inspect configuration files, including `.gitmodules`, prior to initializing nested modules.

3. Isolate repository cloning operations within unprivileged containers or dedicated sandboxes to restrict the impact of potential arbitrary execution.

Caveats:

Automated build processes that rely on automatic retrieval of nested repository structures without recursive flags will require manual verification and isolated processing, which may disrupt automated workflows.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10gitAffected
Red Hat Enterprise Linux 6gitAffected
Red Hat Enterprise Linux 7gitAffected
Red Hat Enterprise Linux 8gitAffected
Red Hat Enterprise Linux 9gitAffected
Red Hat Hardened ImagesgitAffected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Dev Spacesdevspaces/code-rhel9Affected
Red Hat OpenShift Dev Spacesdevspaces/pluginregistry-rhel9Not affected
Red Hat Satellite 6rubygem-gitAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-111760.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON