CVE
Git remote code execution in recursive submodule clones
Affects Git clones made with --recurse-submodules from attacker-hosted repositories. Fixed in 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1 and 2.56.1 on their respective branches.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, and 2 more
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The attacker must supply a repository hosted by the attacker rather than on a normal forge site. The victim must clone with the recursive-submodule option (git clone --recurse-submodules).
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 4 proofs of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Git, a distributed revision control system, contains a flaw that lets an attacker run code on a user's system. The attacker needs only low privileges and must host a malicious repository that the user clones with the recursive submodule option.
Original description
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.
Who should check
Anyone running git clone --recurse-submodules on repositories from untrusted sources not hosted on a normal forge; the affected product is Git.
“can be crafted in a way that exploits a bug in Git”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9/10CVSS 8.0, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The attacker must supply a repository hosted by the attacker rather than on a normal forge site. The victim must clone with the recursive-submodule option (git clone --recurse-submodules).Upgrade to a fixed version: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, or one of 2 more.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-111760 (Git: Recursive clones are susceptible to Remote Code Execution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-111760 (entry last updated 2026-11-17):
Affected:
- git git: fixed in 2.50.2; from 2.51.0, fixed in 2.51.3; from 2.52.0, fixed in 2.52.1; from 2.53.0, fixed in 2.53.1; from 2.54.0, fixed in 2.54.1; from 2.55.0, fixed in 2.55.1; from 2.56.0, fixed in 2.56.1
Fixed versions: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, 2.56.1.
Conditions (all must be true for the bug to be hit):
- The attacker must supply a repository hosted by the attacker rather than on a normal forge site. (source: https://github.com/git/git/security/advisories/GHSA-vp2w-7xxj-jvxr)
- The victim must clone with the recursive-submodule option (git clone --recurse-submodules). (source: https://github.com/git/git/security/advisories/GHSA-vp2w-7xxj-jvxr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-111760 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111760 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/git/git/security/advisories/GHSA-vp2w-7xxj-jvxr
- https://github.com/git/git/commit/29411cf59fd417d8fce1be40ab2911e3e0885f26
- https://gitlab.com/git-scm/git/-/blob/v2.50.2/Documentation/RelNotes/2.50.2.adoc
- https://gitlab.com/git-scm/git/-/blob/v2.51.3/Documentation/RelNotes/2.51.3.adoc
- https://gitlab.com/git-scm/git/-/blob/v2.52.1/Documentation/RelNotes/2.52.1.adoc
- https://gitlab.com/git-scm/git/-/blob/v2.53.1/Documentation/RelNotes/2.53.1.adoc
- https://gitlab.com/git-scm/git/-/blob/v2.54.1/Documentation/RelNotes/2.54.1.adoc
- https://gitlab.com/git-scm/git/-/blob/v2.55.1/Documentation/RelNotes/2.55.1.adoc
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-111760
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-111760"}.Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- git git
fixed in 2.50.2; From 2.51.0 · fixed in 2.51.3; From 2.52.0 · fixed in 2.52.1; From 2.53.0 · fixed in 2.53.1; From 2.54.0 · fixed in 2.54.1; From 2.55.0 · fixed in 2.55.1; From 2.56.0 · fixed in 2.56.1
Evidence 15
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 4
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
- Exploit
- Exploit
- Exploit
Other links · 8
- Repository
- Link
- Link
- Link
- Link
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111760
Is CVE-2026-111760 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A cloned repository can supply config or hooks, reached through a symlink, that carry attacker-specified code. That code may run on the cloning user's system.Source: github.com
Which versions are affected by CVE-2026-111760?
git: before 2.50.2; from 2.51.0 before 2.51.3; from 2.52.0 before 2.52.1; from 2.53.0 before 2.53.1; from 2.54.0 before 2.54.1; from 2.55.0 before 2.55.1; from 2.56.0 before 2.56.1.Source: cve.now feed data
Am I affected, and how do I check?
Git versions before 2.50.2, 2.51.0 through 2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0, and 2.56.0 are in the affected ranges. The bug is only believed to trigger when a clone uses git clone --recurse-submodules on a repository hosted by an attacker rather than a normal forge site; check the installed version with git --version.Source: github.com
How do I fix CVE-2026-111760?
Upgrade Git to the fixed version for its branch: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, or 2.56.1.Source: github.com