CVERadar
HIGH · CVSS 3.1 8Public PoCEPSS n/aThreat level 44

CVE-2026-111760: CVE-2026-111760: Git is a fast, scalable, distributed revision control system with an unusually rich comman…

Unknown · Git · NVD published 2026-11-17 · posted 2026-11-16 · last modified 2026-11-17

CVE-2026-111760 at a glance

CVE-2026-111760 is a high-severity Link Following vulnerability in Git, with a CVSS 3.1 base score of 8. NVD published it on 2026-11-17 and classifies the weakness as CWE-59. Public exploit code: 4 public GitHub proof-of-concept repositories from 3 accounts, with the earliest exploit evidence dated 2026-11-16. NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 44/100.

What it is

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.

WeaknessCWE-59 definition
CVSS vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H (source: GitHub)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2026-11-16 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

4 public repositories from 3 accounts, first seen 2026-11-16. Most starred: suominen/CVE-2026-111760 (0 stars), view the suominen/CVE-2026-111760 repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources