Git's November 10, 2026 advisory says the known trigger involves the --recurse-submodules option and a repository hosted by the attacker. The project rates the issue High at CVSS 3.1 8.0.The advisory lists all Git versions as affected and lists no patched version as of November 15, 2026. Teams can track the advisory alongside their vulnerability intelligence platform workflow, while avoiding recursive clones from untrusted sources.
What it allows
How Can CVE-2026-111760 Lead to Code Execution?
Git says an attacker can prepare a repository so Git overwrites a submodule gitfile with a symbolic link. That link can direct Git toward attacker-supplied configuration or hooks, which may contain code chosen by the attacker. This explains the possible remote code execution outcome without establishing that every clone is exposed.
The advisory narrows its current assessment to repositories hosted by the attacker and clones using --recurse-submodules. Git says it currently believes this option is required. The statement is a current assessment, so teams should watch the advisory for changes.
How Should Teams Interpret Current Risk?
Brandefense Blackhole counted six dark-chat items matching CVE-2026-111760 from August 17 through November 15, 2026. A GitHub repository search returned three public repositories named for this CVE on November 15. These are separate counts of matching items, and neither count verifies exploitation or an incident.
CISA's November 13, 2026 Known Exploited Vulnerabilities catalog did not list the CVE. Catalog status does not establish whether an individual environment has been compromised. Review exposure to attacker-controlled repositories before interpreting these signals as a reason to change priorities.
Who is affected
Which Git Versions and Workflows Are Affected?
Git's advisory marks all versions of Git as affected and names no patched release as of November 15, 2026. It does not give version branch boundaries suitable for an automatic version check. The relevant exposure is a recursive clone of an attacker-hosted repository, rather than one on a normal forge site, according to Git's current assessment.
Inventory developer workstations and automation that clone untrusted repositories. Check whether those jobs enable --recurse-submodules, especially when the repository source is controlled by an external party. A normal clone without that option is outside Git's stated trigger assessment, but the advisory may change as patches are discussed.
What Should Teams Do Until a Fix Is Available?
Git recommends avoiding clones from untrusted sources, and it says patches are being discussed on the git-security mailing list. Suspend recursive cloning for untrusted repositories, including in development and CI workflows. Record where the option is still used so owners can reassess those jobs when a fix is released.
Review available clone-job and endpoint activity for unexpected execution after a recursive clone of an untrusted repository. This is Brandefense defensive guidance, not a Git detection signature. When Git publishes a fixed release, install it and verify the running Git version on each affected workstation and runner. Keep the recorded clone jobs under review as Git updates its advisory.
Timeline
- 2026-11-10
The Git project published GHSA-vp2w-7xxj-jvxr for CVE-2026-111760.
What to do
-
Find recursive clones of untrusted repositories
Inventory developer and CI jobs that clone external repositories. Identify where --recurse-submodules is enabled and who controls each repository source.
-
Suspend the risky clone path
Avoid cloning repositories from untrusted sources, as Git advises. Suspend recursive clones of attacker-controlled or otherwise untrusted repositories while the advisory lists no fix.
-
Review relevant execution activity
Investigate unexpected execution after recursive clones from untrusted sources. This is Brandefense defensive guidance; Git does not publish a detection signature in the advisory.
-
Track a fix and verify it after release
Recheck the Git advisory for a patched release. When one is published, deploy it. Run git --version on each workstation and CI runner, then compare the output with Git's fixed release.
What Brandefense can do
- Scan your domain in Brandefense Atlas, free
Atlas checks public sources for leaked credentials, phishing domains, dark web mentions and data sales, then gives your domain a risk grade. Free, no sign-up.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-111760 affect every Git version?
Git's advisory currently lists all versions as affected. It does not identify a patched version or branch-specific range as of November 15, 2026.
Is every Git clone vulnerable to this attack path?
Git currently believes the trigger requires --recurse-submodules and an attacker-controlled repository. The advisory does not state that ordinary clones share this trigger.
Has Git released a fix for CVE-2026-111760?
The November 10 advisory still lists patched versions as none on November 15, 2026. Git says patches are being discussed on its security mailing list.
Do online mentions prove exploitation?
No. Brandefense Blackhole counted six matching dark-chat items during August 17 to November 15, while GitHub search returned three named repositories. These counts do not validate an exploit or incident.
