CVSS 3.1
8.0 highCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:HHigh (8.0) in git git. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| 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 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | git | no fix listed | DEBIAN-CVE-2026-111760 |
| Ubuntu | 22.04:LTS, 24.04:LTS, 26.04:LTS and 4 more | git | no fix listed | UBUNTU-CVE-2026-111760 |
| openSUSE | Tumbleweed | git | 2.56.1-1.1 | openSUSE-SU-2026:12538-1 |
| Alpine | v3.23 | git | 2.52.1-r0 | ALPINE-CVE-2026-111760 |
| Alpine | v3.24 | git | 2.54.1-r0 | ALPINE-CVE-2026-111760 |
| Azure Linux | 3 | git | no fix listed | AZL-114293 |
| Alpaquita | 23 | git | 2.43.7-r1 | BELL-CVE-2026-111760 |
| Alpaquita | 25 | git | 2.50.2-r0 | BELL-CVE-2026-111760 |
| Alpaquita | stream | git | 2.56.1-r0 | BELL-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 rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | git | Affected | |
| Red Hat Enterprise Linux 6 | git | Affected | |
| Red Hat Enterprise Linux 7 | git | Affected | |
| Red Hat Enterprise Linux 8 | git | Affected | |
| Red Hat Enterprise Linux 9 | git | Affected | |
| Red Hat Hardened Images | git | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Affected | |
| Red Hat OpenShift Dev Spaces | devspaces/code-rhel9 | Affected | |
| Red Hat OpenShift Dev Spaces | devspaces/pluginregistry-rhel9 | Not affected | |
| Red Hat Satellite 6 | rubygem-git | Affected |
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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.