CVE-2026-111760

HIGHPre-NVD 8.08.0
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source

Also known asEUVD-2026-126653 (ENISA EUVD)Source: ENISA EUVD

8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.0
EG Score
8.0HIGHlow confidence
EG Risk
36
EG Risk 36/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 17, 2026

Advisory Details (9)

Auto-updated Nov 16, 2026
Patch available. Sources: github, github_commit.
Web page

Documentation/RelNotes/2.56.1.adoc · v2.56.1 · git-scm / Git · GitLab

https://gitlab.com/git-scm/git/-/blob/v2.56.1/Documentation/RelNotes/2.56.1.adoc
Web page

Documentation/RelNotes/2.55.1.adoc · v2.55.1 · git-scm / Git · GitLab

https://gitlab.com/git-scm/git/-/blob/v2.55.1/Documentation/RelNotes/2.55.1.adoc
Web page

Documentation/RelNotes/2.54.1.adoc · v2.54.1 · git-scm / Git · GitLab

https://gitlab.com/git-scm/git/-/blob/v2.54.1/Documentation/RelNotes/2.54.1.adoc
Web page

Documentation/RelNotes/2.53.1.adoc · v2.53.1 · git-scm / Git · GitLab

https://gitlab.com/git-scm/git/-/blob/v2.53.1/Documentation/RelNotes/2.53.1.adoc
Web page

Documentation/RelNotes/2.52.1.adoc · v2.52.1 · git-scm / Git · GitLab

https://gitlab.com/git-scm/git/-/blob/v2.52.1/Documentation/RelNotes/2.52.1.adoc
Web page

Documentation/RelNotes/2.51.3.adoc · v2.51.3 · git-scm / Git · GitLab

https://gitlab.com/git-scm/git/-/blob/v2.51.3/Documentation/RelNotes/2.51.3.adoc
Web page

Documentation/RelNotes/2.50.2.adoc · v2.50.2 · git-scm / Git · GitLab

https://gitlab.com/git-scm/git/-/blob/v2.50.2/Documentation/RelNotes/2.50.2.adoc
GitHub commit

commit 29411cf59fd4 (git/git)

Fix landed in git/git commit 29411cf59fd4 — awaiting tagged release

https://github.com/git/git/commit/29411cf59fd417d8fce1be40ab2911e3e0885f26
GitHub advisoryMentions a patch (unverified)

Recursive clones are susceptible to Remote Code Execution · Advisory · git/git · GitHub

https://github.com/git/git/security/advisories/GHSA-vp2w-7xxj-jvxr

Vendor Advisories for CVE-2026-111760(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  3. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-11-19 09:26 UTCOSV refresh
  5. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  7. 2026-11-17 05:31 UTCEchelonGraph re-scored
  8. 2026-11-17 05:00 UTCEchelonGraph re-scored
  9. 2026-11-16 22:30 UTCEchelonGraph re-scored
  10. 2026-11-16 22:02 UTCENISA EUVD ID recordedEUVD-2026-126653 · Source: ENISA EUVD
  11. 2026-11-16 21:28 UTCEchelonGraph re-scored
  12. 2026-11-16 21:06 UTCEchelonGraph re-scoredFirst assessed: 8.0 HIGH
  13. 2026-11-16 21:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-111760?
CVE-2026-111760 is a high-severity vulnerability; its CVE record was published on November 16, 2026. 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…
When was the CVE record for CVE-2026-111760 published?
The CVE record for CVE-2026-111760 was published on November 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-111760 actively exploited?
CVE-2026-111760 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111760?
CVE-2026-111760 has a CVSS base score of 8.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-111760?
A fix for CVE-2026-111760 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111760 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-111760

Explore →

Is Your Infrastructure Affected by CVE-2026-111760?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.