Sign inStart freeBook a demo

GitLab vulnerabilities4 known to be exploited.

Vendor4 known exploited
The short answer

GitLab has 1,199 published vulnerabilities across 9 products in our catalogue. 4 of them are on the list of flaws known to be exploited, so criminals are using them now. The most affected product is GitLab, with 1,186. If you run GitLab software, patch the exploited flaws first.

See the exploited flaws

The most recent GitLab flaw added to the known-exploited list is CVE-2021-22175, on 18 February 2026. We keep watching the known-exploited list.

Products

Which GitLab products have the most vulnerabilities?

GitLab leads with 1,186 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. GitLab1,186
  2. Gitlab-Shell5
  3. Dynamic Application Security Testing Analyzer4
  4. Runner3
  5. Gitlab-Vscode-Extension2
  6. Gitlab Runner1
  7. Gitaly1
  8. Dast API Scanner1
  9. Omnibus1
Published vulnerabilities
Known exploited

Which GitLab vulnerabilities are being exploited?

4 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 9.8
    CVE-2021-22175CriticalKnown exploited
    GitLab Server-Side Request Forgery (SSRF) Vulnerability

    GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled.

    Chance of use53%Known exploited since18 Feb 2026
  2. 7.5
    CVE-2021-39935HighKnown exploited
    GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) Vulnerability

    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.

    Chance of use36%Known exploited since3 Feb 2026
  3. 10.0
    CVE-2023-7028CriticalKnown exploited
    GitLab Community and Enterprise Editions Improper Access Control Vulnerability

    GitLab Community and Enterprise Editions contain an improper access control vulnerability.

    Chance of use95%Known exploited since1 May 2024
  4. 10.0
    CVE-2021-22205CriticalKnown exploited
    GitLab Community and Enterprise Editions Remote Code Execution Vulnerability

    GitHub Community and Enterprise Editions that utilize the ability to upload images through GitLab Workhorse are vulnerable to remote code execution.

    Chance of use>99%Known exploited since3 Nov 2021
Exploit likelihood

Which GitLab flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2021-22205CriticalKnown exploited

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.

    CVSS10.0Published23 Apr 2021
  2. 96%
    CVE-2023-2442High

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.11 before 15.11.7, all versions starting from 16.0 before 16.0.2.

    CVSS8.7Published7 Jun 2023
  3. 95%
    CVE-2023-7028CriticalKnown exploited

    An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.3 prior to 16.3.7, 16.4 prior to 16.4.5, 16.5 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7...

    CVSS10.0Published12 Jan 2024
  4. 92%
    CVE-2023-0050Medium

    An issue has been discovered in GitLab affecting all versions starting from 13.7 before 15.7.8, all versions starting from 15.8 before 15.8.4, all versions starting from 15.9 before 15.9.2.

    CVSS5.4Published9 Mar 2023
  5. 88%
    CVE-2022-1190Medium

    Improper handling of user input in GitLab CE/EE versions 8.3 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allowed an attacker to exploit a stored XSS by abusing multi-word milestone references in...

    CVSS5.4Published4 Apr 2022
  6. 87%
    CVE-2022-3265High

    A cross-site scripting issue has been discovered in GitLab CE/EE affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.

    CVSS7.3Published9 Nov 2022
  7. 86%
    CVE-2022-2992Critical

    A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows an authenticated user to achieve remote code execution via the Import from GitHub API endpoint.

    CVSS9.9Published17 Oct 2022
  8. 84%
    CVE-2023-0921Medium

    A lack of length validation in GitLab CE/EE affecting all versions from 8.3 before 15.10.8, 15.11 before 15.11.7, and 16.0 before 16.0.2 allows an authenticated attacker to create a large Issue description via...

    CVSS4.3Published6 Jun 2023
  9. 82%
    CVE-2022-1175Medium

    Improper neutralization of user input in GitLab CE/EE versions 14.4 before 14.7.7, all versions starting from 14.8 before 14.8.5, all versions starting from 14.9 before 14.9.2 allowed an attacker to exploit XSS by...

    CVSS6.1Published4 Apr 2022
  10. 80%
    CVE-2021-4191Medium

    An issue has been discovered in GitLab CE/EE affecting versions 13.0 to 14.6.5, 14.7 to 14.7.4, and 14.8 to 14.8.2.

    CVSS5.3Published28 Mar 2022
Every product

All GitLab products we track.

8 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

This directory lists the 8 GitLab products with at least one tracked version, of 9 in our catalogue.

Precursor Intelligence

Running GitLab? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 1,199 published vulnerabilities across 9 products and 1,879 versions from GitLab. The most recent GitLab flaw added to the known-exploited list is CVE-2021-22175, on 18 February 2026.

4 GitLab vulnerabilities are on the list of flaws known to be exploited. The most recently added are CVE-2021-22175, CVE-2021-39935 and CVE-2023-7028. The full list is on this page.

GitLab, with 1,186 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the GitLab products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.

Keep exploring