GitLab vulnerabilitiesRanked by how likely they are to be used.
GitLab is made by Jenkins. We track 6 published vulnerabilities listed under that exact name, across 122 versions. None of them is on the list of flaws known to be exploited today. Jenkins lists newer releases under their own names, such as Gitlab Authentication, so check those pages too.
We keep watching the known-exploited list.
Is GitLab listed under other names? Yes.
Jenkins also lists GitLab under more specific names, such as Gitlab Authentication and Gitlab Hook. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which GitLab vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of GitLab's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
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.
- 73%CVE-2022-34777Medium
Jenkins GitLab Plugin 1.5.34 and earlier does not escape multiple fields inserted into the description of webhook-triggered builds, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by...
- 1.3%CVE-2019-10301High
A missing permission check in Jenkins GitLab Plugin 1.5.11 and earlier in the GitLabConnectionConfig#doTestConnection form validation method allowed attackers with Overall/Read permission to connect to an...
- 1.3%CVE-2019-10300High
A cross-site request forgery vulnerability in Jenkins GitLab Plugin 1.5.11 and earlier in the GitLabConnectionConfig#doTestConnection form validation method allowed attackers to connect to an attacker-specified URL...
- 0.9%CVE-2022-30955Medium
Jenkins GitLab Plugin 1.5.31 and earlier does not perform a permission check in an HTTP endpoint, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
- 0.8%CVE-2022-43411Medium
Jenkins GitLab Plugin 1.5.35 and earlier uses a non-constant time comparison function when checking whether the provided and expected webhook token are equal, potentially allowing attackers to use statistical methods...
- 0.3%CVE-2025-24397Medium
An incorrect permission check in Jenkins GitLab Plugin 1.9.6 and earlier allows attackers with global Item/Configure permission (while lacking Item/Configure permission on any particular job) to enumerate credential...
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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Jenkins GitLab Plugin 1.5.34 and earlier does not escape multiple fields inserted into the description of webhook-triggered builds, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
- Matched to
- GitLab on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 6 published vulnerabilities listed under the name GitLab, across 122 versions.
None of GitLab's vulnerabilities is on the list of flaws known to be exploited today.
Jenkins also lists GitLab under more specific names, such as Gitlab Authentication and Gitlab Hook. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track GitLab. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.