Threadlinqs IntelligenceStart free

Vendor2 products tracked

GitLab vulnerabilities & exploitation

5 in CISA KEV1 ransomware-linked9 with public exploit

As of 2026-11-19, Threadlinqs tracks 37 GitLab CVEs, 5 in the CISA Known Exploited Vulnerabilities catalog, 1 used in ransomware campaigns, linked to 26 tracked threat campaigns and 5 named threat actors.

CVEs
37Since 2021
CISA KEV
514% of CVEs
Critical
11CVSS v3 9.0+
Avg CVSS
7.2/10Max 10
Threats
26Linked campaigns
Actors
5Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 37 GitLab CVEs published between and . The busiest month was 2026-07 (13 new CVEs). 5 of them (14%) are listed in CISA KEV, which means exploitation in the wild has been confirmed.

Most exploited vulnerabilities

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

Products affected

Threadlinqs normalises CPE and CNA product records across all 37 CVEs; 2 distinct GitLab products are affected. The most frequently affected:

  • GitLab 35 CVEs
  • AI Gateway 2 CVEs

Threat activity

26 tracked threat campaigns reference GitLab products or exploit GitLab CVEs; the 25 most recent are listed.

Threat actors targeting GitLab

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

How to prioritise GitLab patching

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

  • 5 of 37 GitLab CVEs (14%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2021-22205, CVE-2023-7028, CVE-2021-39935.
  • 1 CVE is known to be used in ransomware campaigns; patch these ahead of other KEV entries on internet-facing systems.
  • Outside KEV, the highest EPSS scores are CVE-2026-110264 (1.3%), CVE-2026-90970 (0.9%), CVE-2026-3988 (0.9%).
  • 11 CVEs score Critical and 10 High on CVSS v3 (maximum 10, average 7.2); sequence these after KEV and high-EPSS items.
  • 9 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.