GitLab vulnerabilities in CISA KEV
GitLab has 6 vulnerabilities in CISA's catalogue of flaws known to be exploited, the 40th highest of any vendor. 4 were added in the last 12 months; 1 is linked to known ransomware use (16.7% of its entries, against 20.4% across the catalogue). CISA's median fix window for these entries is 17.5 days (range 3 to 21), against 21 days (range 1 to 184) across the whole catalogue. The most exploited product is Community and Enterprise Editions, with 2 entries. Other frequently affected products: Community Edition and Enterprise Edition (2); GitLab (1).
Catalog v2026.11.04, released 5 Nov 2026. Source CISA ↗. All KEV entries.
$ ./kev --vendor gitlab --summary
Counts are computed from the catalog release on ; the 12 month window ends there.
┌─ total entries
6
in CISA KEV
┌─ first added
2021-11-03
earliest entry
┌─ latest added
2026-10-29
most recent entry
┌─ last 12 months
4
entries added
┌─ ransomware use
1 of 6
16.7% linked to ransomware
┌─ distinct products
4
affected products
$ awk -F, {print $1} /var/log/kev/gitlab.log | uniq -c
Entries by the year CISA added them.
| Year | Entries added | Of which ransomware |
|---|---|---|
| 2021 | 1 | 1 |
| 2024 | 1 | 0 |
| 2026 | 4 | 0 |
$ sort /var/log/kev/gitlab.log | uniq -c | sort -rn | head -5
The five products with the most entries in the catalogue.
- Community and Enterprise Editions 2 entries
- Community Edition and Enterprise Edition 2 entries
- GitLab 1 entry
- GitLab CE/EE 1 entry
$ kev-due-dates --vendor gitlab
Days between the date CISA added an entry and the due date it set, median and range. Due dates apply to US federal agencies; for everyone else they are a patch-first ranking signal.
┌─ GitLab
17.5 days (range 3 to 21)
median and range in days
┌─ whole catalogue
21 days (range 1 to 184)
median and range in days
$ grep -o 'CWE-[0-9]*' /var/log/kev/gitlab.log | sort | uniq -c | sort -rn | head -3
Weakness types CISA records for these entries (6 of 6 have at least one CWE).
$ grep -ril 'GitLab' /var/log/news | head -5
Our reporting that names GitLab or one of its KEV CVE ids, newest first.
┌─ /var/log/news
Patch Week pages with these entries
$ wc -l ./gitlab.kev · 6 rows
Descriptions: CISA Known Exploited Vulnerabilities catalogue
- CVE-2026-97229
Community Edition and Enterprise Edition
GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability
due 2026-11-01 · CWE-190
$ cat CVE-2026-97229.txt
Description. GitLab Community Edition and Enterprise Edition contain a integer overflow or wraparound vulnerability that could allow an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration, due to insufficient regular expression validation.
Required action. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- CVE-2026-85706
Community Edition and Enterprise Edition
GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
due 2026-09-14 · CWE-35
$ cat CVE-2026-85706.txt
Description. GitLab Community Edition and Enterprise Edition contains a path traversal vulnerability that allows an unauthenticated user to read arbitrary files due to an improper path confinement and missing authentication enforcement in the repository commits API.
Required action. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- CVE-2021-22175
GitLab
GitLab Server-Side Request Forgery (SSRF) Vulnerability
due 2026-03-11 · CWE-918
$ cat CVE-2021-22175.txt
Description. GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled.
Required action. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- CVE-2021-39935
Community and Enterprise Editions
GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) Vulnerability
due 2026-02-24 · CWE-918
$ cat CVE-2021-39935.txt
Description. GitLab Community and Enterprise Editions contain a server-side request forgery vulnerability which could allow unauthorized external users to perform Server Side Requests via the CI Lint API.
Required action. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- CVE-2023-7028
GitLab CE/EE
GitLab Community and Enterprise Editions Improper Access Control Vulnerability
due 2024-05-22 · CWE-284
$ cat CVE-2023-7028.txt
Description. GitLab Community and Enterprise Editions contain an improper access control vulnerability. This allows an attacker to trigger password reset emails to be sent to an unverified email address to ultimately facilitate an account takeover.
Required action. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- CVE-2021-22205
Community and Enterprise Editions [RANSOMWARE]
GitLab Community and Enterprise Editions Remote Code Execution Vulnerability
due 2021-11-17 · CWE-20 CWE-95
$ cat CVE-2021-22205.txt
Description. GitHub Community and Enterprise Editions that utilize the ability to upload images through GitLab Workhorse are vulnerable to remote code execution. Workhorse passes image file extensions through ExifTool, which improperly validates the image files.
Required action. Apply updates per vendor instructions.