Threadlinqs IntelligenceStart free

Vendor1 product tracked

Git vulnerabilities & exploitation

2 with public exploit

As of 2026-11-19, Threadlinqs tracks 6 Git CVEs, 0 in the CISA Known Exploited Vulnerabilities catalog, linked to 4 tracked threat campaigns and 5 named threat actors.

CVEs
6Since 2026
CISA KEV
00% of CVEs
Critical
0CVSS v3 9.0+
Avg CVSS
5.1/10Max 8
Threats
4Linked campaigns
Actors
5Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 6 Git CVEs published between and . The busiest month was 2026-11 (6 new CVEs). None of them is listed in CISA KEV yet.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 6 of 6 tracked Git CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 6 CVEs; 1 distinct Git product is affected. The most frequently affected:

  • Git 6 CVEs

Threat activity

4 tracked threat campaigns reference Git products or exploit Git CVEs:

Threat actors targeting Git

Named threat actors attributed to campaigns that involve Git products or CVEs, with the number of linked campaigns:

How to prioritise Git patching

This order follows the data Threadlinqs holds for Git, not a generic severity checklist:

  • No Git CVE is in CISA KEV yet, so rank by exploit probability instead.
  • 0 CVEs score Critical and 2 High on CVSS v3 (maximum 8, average 5.1); sequence these after KEV and high-EPSS items.
  • 2 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-11-19 and refresh daily.