Threadlinqs IntelligenceStart free

Vendor1 product tracked

gitpython-developers vulnerabilities & exploitation

2 with public exploit

As of 2026-11-19, Threadlinqs tracks 6 gitpython-developers CVEs, 0 in the CISA Known Exploited Vulnerabilities catalog, linked to 1 tracked threat campaign.

CVEs
6Since 2026
CISA KEV
00% of CVEs
Critical
0CVSS v3 9.0+
Avg CVSS
7.4/10Max 8.1
Threats
1Linked campaigns
Actors
0None attributed

Data as of:

Exploitation timeline

Threadlinqs has recorded 6 gitpython-developers CVEs published between and . The busiest month was 2026-10 (5 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 gitpython-developers CVEs.

Products affected

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

  • GitPython 6 CVEs

Threat activity

1 tracked threat campaign reference gitpython-developers products or exploit gitpython-developers CVEs:

How to prioritise gitpython-developers patching

This order follows the data Threadlinqs holds for gitpython-developers, not a generic severity checklist:

  • No gitpython-developers CVE is in CISA KEV yet, so rank by exploit probability instead.
  • Outside KEV, the highest EPSS scores are CVE-2026-110858 (0.5%), CVE-2026-114145 (0.4%), CVE-2026-67322 (0.3%).
  • 0 CVEs score Critical and 5 High on CVSS v3 (maximum 8.1, average 7.4); 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.