Skip to main content
Mallory
HighVulnerability

CVE-2026-111760: Remote Code Execution in Git Recursive Submodule Cloning

Published Nov 16, 2026 · Updated today
Trending this week#24of 428,771 vulnerabilities
Mention activity · 30 days62 mentions · peak 20 in a dayToday
CVSS8.0High · v3.1
EPSS0.71%54th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-111760CWE-59 · Improper Link Resolution Before…

CVE-2026-111760 is a remote code execution vulnerability in Git's handling of recursive submodule clones. An excessively long pathname passes validation before its length is truncated in the 32-bit ce_namelen field, causing Git to write a shorter pathname than the one validated. A crafted repository can exploit this discrepancy to replace a submodule gitfile with a symbolic link targeting attacker-controlled Git configuration or hooks. Subsequent use of that metadata can execute attacker-specified code during cloning.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation executes arbitrary code with the privileges of the user or automation account performing the clone, compromising the confidentiality, integrity, and availability of resources accessible to that account. Developer workstations and CI workers may expose source code, credentials, build artifacts, and other accessible data. Execution occurs during recursive cloning; opening project files or running setup scripts is not required.

Mitigation

If you can’t patch tonight, do this now.

Until patched, clone only from trusted servers and avoid recursive submodule cloning of untrusted repositories. Initially clone unfamiliar projects without recursive submodule initialization, then inspect submodule sources and selected commits before fetching them, resolving relative repository addresses against the parent repository's address. Restrict CI submodule sources to expected repositories. Evaluate unfamiliar repositories in disposable, least-privileged environments without SSH keys, cloud tokens, deployment credentials, or production data. These precautions do not replace patching.

Remediation

Patch, then assume compromise.

Upgrade Git to the fixed release for the installed maintenance line: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, or 2.56.1, or a later patched release. Vendor packages with documented backported fixes are also suitable. The fix rejects excessively long index paths before pathname lengths can be truncated. Update all Git installations, including copies bundled with applications, containers, build images, and automation services; verify vendor advisories and package changelogs rather than relying solely on upstream version numbers.

Public exploits

Exploits

No validated public exploits yet. Hidden: 4 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2026-111760 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-111760 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-111760?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-111760.
Is there a patch for CVE-2026-111760?
Upgrade Git to the fixed release for the installed maintenance line: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, or 2.56.1, or a later patched release. Vendor packages with documented backported fixes are also suitable.
How severe is CVE-2026-111760?
CVE-2026-111760 has a CVSS v3.1 score of 8.0 (High) and an EPSS score of 0.71% (54th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

62 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 17, 2026CentOS Linux 7 [TuxCare] Security Update: emacs-git / emacs-gi... | Tenable®A vulnerability covered by the TuxCare emacs-git security update for CentOS Linux 7. The excerpt reports available exploits and a patch publication date of November 12, 2026, but does not describe the vulnerability's technical cause or impact.Read more ↗cvefeed high severityNews · Nov 16, 2026CVE-2026-111760 - Git: Recursive clones are susceptible to Remote Code ExecutionA high-severity Git remote code execution vulnerability rated CVSS 3.1 8.0. When a user recursively clones an attacker-hosted repository, Git can overwrite a submodule gitfile with a symbolic link pointing to attacker-controlled configuration or hooks, enabling code execution on the user's system. Fixed versions are 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1. The content recommends avoiding untrusted repositories and using recursive-submodule cloning cautiously.Read more ↗krcert kisaNews · Nov 16, 2026Git 제품 보안 업데이트 권고 > 보안공지 > 알림마당 : KISA 보호나라&KrCERT/CCA vulnerability in Git whose technical cause and impact are not specified in the advisory. Users are advised to update to a fixed release. Listed fixed versions are 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1 for the corresponding release branches.Read more ↗gitlabNews · Nov 16, 2026Documentation/RelNotes/2.50.2.adoc · v2.50.2 · git-scm / Git · GitLabA malicious repository can cause Git, during a recursive clone, to overwrite a submodule gitfile with a symbolic link pointing to a directory containing attacker-controlled configuration or hooks. This can lead to remote code execution. Git 2.50.2 addresses the vulnerability.Read more ↗
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity42Community discussion across Reddit, Mastodon, and other social sources.