Git Advisory Prompts Restrictions on Recursive Clones From Untrusted Sources

Git’s November 10, 2026 security advisory identifies CVE-2026-111760, a high-severity vulnerability that may allow remote code execution when a crafted repository hosted by an attacker is recursively cloned. The Git project’s current assessment says the flaw can be triggered when the --recurse-submodules option is used. The advisory does not describe ordinary clones as exposed in the same way, so organizations should focus immediate review on recursive-clone operations rather than treating all Git activity as equally affected. As of November 15, Git lists all versions as affected and no patched version, leaving organizations without a stated fixed release to deploy.

The reported mechanism makes this a software supply-chain concern for development environments and automated build pipelines. According to the source material, a crafted repository can cause a submodule gitfile to be overwritten with a symbolic link. The link can point to a directory containing attacker-specified configuration or hooks, which may contain executable code. Git rates the issue High, with a CVSS 3.1 score of 8.0; no CVSS 4.0 score is listed. The interim control identified in the advisory is to avoid cloning repositories from untrusted sources while a patch is unavailable.

For federal agencies, prime contractors, and subcontractors, the advisory is relevant wherever Git is used to support government software development, integration, testing, or delivery. Repository owners and CI teams should locate scripts, jobs, and developer instructions that invoke recursive cloning, then determine which external sources could be changed by parties outside the organization. This is a workflow-specific review: the supplied information does not establish that every government system or every Git deployment is exposed. It does, however, give procurement and security teams a concrete issue to raise in software supply-chain risk reviews and vendor discussions about development and delivery practices.

Organizations should assign an accountable owner to monitor the Git project advisory and verify any fix against the project’s release information before relaxing interim controls. Where work cannot pause, source approval should be an explicit decision by a named owner, with exceptions documented and revisited. The source recommends reviewing recent use of the recursive option in automated jobs and asking owners whether any source came from an attacker-controlled host. The signal identifies no patch, remediation deadline, or separate federal directive; CISA is listed in the supplied agency data, but the source does not attribute the technical advisory to CISA. Teams should therefore distinguish the Git project’s stated facts from operational recommendations derived from them.

• Vulnerability: CVE-2026-111760 may permit remote code execution during recursive cloning of an attacker-controlled repository.
• Trigger identified: Git’s current assessment points to use of --recurse-submodules; the source does not describe ordinary clones as exposed in the same way.
• Affected scope: Git lists all versions as affected as of November 15, 2026; no patched version is listed.
• Severity: Git rates the issue High, with a CVSS 3.1 score of 8.0 and no CVSS 4.0 score listed.
• Reported mechanism: A crafted repository may overwrite a submodule gitfile with a symbolic link leading to attacker-specified configuration or hooks that may contain code.
• Interim control: Avoid recursive clones from untrusted sources while no patch is available; document any approved exceptions.
• Workflow review: Inventory developer instructions, scripts, and CI jobs that perform recursive clones, and identify who controls each source and who approves it.
• Federal contracting action: Procurement and security teams can assess whether development and delivery workflows supporting government work rely on the affected operation.
• Monitoring: Assign an owner to track Git’s advisory and confirm a released fix before changing restrictions; no patch or remediation deadline is identified in the signal.