Skip to main content
VulnerabilityPublished

CVE-2026-111760: git · Link Following

Affects gitSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.0 High · fixed in 2.56.1 : patch git soon.

Data as of 16 Nov 2026, 21:20 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.0
Patch
Available – fixed in 2.56.1, 2.55.1, 2.54.1 +4
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
gitgitAffected
  • >=2.56.0 <2.56.1
Fixed in
  • 2.56.1
gitgitAffected
  • >=2.55.0 <2.55.1
Fixed in
  • 2.55.1
gitgitAffected
  • >=2.54.0 <2.54.1
Fixed in
  • 2.54.1
gitgitAffected
  • >=2.53.0 <2.53.1
Fixed in
  • 2.53.1
gitgitAffected
  • >=2.52.0 <2.52.1
Fixed in
  • 2.52.1
gitgitAffected
  • >=2.51.0 <2.51.3
Fixed in
  • 2.51.3

AI-suggested

Users should upgrade Git to one of the fixed versions: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, or 2.56.1. Until patched, users should avoid cloning repositories from untrusted sources using the --recurse-submodules option. No other mitigations are specified by the vendor advisory.

Description

A vulnerability in Git prior to versions 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1 allows an attacker-controlled repository to exploit the git clone --recurse-submodules command. This can cause Git to overwrite a submodule gitfile with a symbolic link pointing to attacker-controlled configuration or hooks, potentially leading to code execution on the cloning user's system. The issue requires the use of the recursive-submodule option and untrusted repositories.

References

Community reviews

Loading reviews…