Overview 27 matches · 2 in Waratek scope · 0 protected · 8 exploited · 5 CISA KEV · 14 public PoC
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
1
3.7%
No exploit published
1
3.7%
Outside Waratek scope
0
0.0%
Not applicable
25
92.6%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
27
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
8
29.6%
Working exploit published
6
22.2%
Proof of concept only
3
11.1%
Forecast only
10
37.0%
No public exploit
0
0.0%
split by
peak 10 / year
20191
Not applicable1
Critical1
not blocked1
Working exploit published1
20202
Mitigation candidate1
Not applicable1
High1
Medium1
not blocked2
Exploited1
Forecast only1
20215
Not applicable5
Critical2
High2
Medium1
not blocked5
Exploited2
Forecast only3
202210
No exploit published1
Not applicable9
Critical4
High4
Medium2
not blocked10
Exploited1
Working exploit published5
Proof of concept only1
Forecast only3
20235
Not applicable5
Critical1
High2
Medium2
not blocked5
Exploited1
Proof of concept only2
Forecast only2
20242
Not applicable2
Critical1
High1
not blocked2
Exploited1
Forecast only1
20250
20262
Not applicable2
Critical2
not blocked2
Exploited2
20192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-97229 | Critical | 2026-10-13 | Not applicable | Exploited | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed 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. |
| CVE-2026-85706 | Critical | 2026-09-12 | Not applicable | Exploited | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API. |
| CVE-2024-1451 | High | 2024-02-22 | Not applicable | Forecast only | An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.9 before 16.9.1. A crafted payload added to the user profile page could lead to a stored XSS on the client side, allowing attackers to perform arbitrary actions on behalf of victims." |
| CVE-2023-7028 | Critical | 2024-01-12 | Not applicable | 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 prior to 16.7.2 in which user account password reset emails could be delivered to an unverified email address. |
| CVE-2023-2164 | Medium | 2023-08-02 | Not applicable | Proof of concept only | An issue has been discovered in GitLab affecting all versions starting from 15.9 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. It was possible for an attacker to trigger a stored XSS vulnerability via user interaction with a crafted URL in the WebIDE beta. |
| CVE-2023-2442 | High | 2023-06-07 | Not applicable | Proof of concept only | 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. A specially crafted merge request could lead to a stored XSS on the client side which allows attackers to perform arbitrary actions on behalf of victims. |
| CVE-2023-0921 | Medium | 2023-06-06 | Not applicable | Forecast only | 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 GraphQL which, when repeatedly requested, saturates CPU usage. |
| CVE-2023-2825 | Critical | 2023-05-26 | Not applicable | Exploited | An issue has been discovered in GitLab CE/EE affecting only version 16.0.0. An unauthenticated malicious user can use a path traversal vulnerability to read arbitrary files on the server when an attachment exists in a public project nested within at least five groups. |
| CVE-2023-0050 | High | 2023-03-09 | Not applicable | Forecast only | 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. A specially crafted Kroki diagram could lead to a stored XSS on the client side which allows attackers to perform arbitrary actions on behalf of victims. |
| CVE-2022-3265 | High | 2022-11-09 | Not applicable | Proof of concept only | 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. It was possible to exploit a vulnerability in setting the labels colour feature which could lead to a stored XSS that allowed attackers to perform arbitrary actions on behalf of victims at client side. |
| CVE-2022-2992 | Critical | 2022-10-17 | Not applicable | Working exploit published | 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. |
| CVE-2022-2884 | Critical | 2022-10-17 | Not applicable | Working exploit published | A vulnerability in GitLab CE/EE affecting all versions from 11.3.4 prior to 15.1.5, 15.2 to 15.2.3, 15.3 to 15.3 to 15.3.1 allows an an authenticated user to achieve remote code execution via the Import from GitHub API endpoint |
| CVE-2022-2230 | High | 2022-07-01 | Not applicable | Forecast only | A Stored Cross-Site Scripting vulnerability in the project settings page in GitLab CE/EE affecting all versions from 14.4 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1, allows an attacker to execute arbitrary JavaScript code in GitLab on a victim's behalf. |
| CVE-2022-2185 | Critical | 2022-07-01 | Not applicable | Working exploit published | A critical issue has been discovered in GitLab affecting all versions starting from 14.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 where an authenticated user authorized to import projects could import a maliciously crafted project leading to remote code execution. |
| CVE-2022-34777 | Medium | 2022-06-30 | No exploit published | Forecast only | 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. |
| CVE-2022-1190 | High | 2022-04-04 | Not applicable | Forecast only | 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 issue descriptions, comments, etc. |
| CVE-2022-1175 | High | 2022-04-04 | Not applicable | Working exploit published | 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 injecting HTML in notes. |
| CVE-2022-1162 | Critical | 2022-04-04 | Not applicable | Working exploit published | A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. OAuth, LDAP, SAML) in GitLab CE/EE versions 14.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allowing attackers to potentially take over accounts |
| CVE-2021-4191 | Medium | 2022-03-28 | Not applicable | Exploited | 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. Private GitLab instances with restricted sign-ups may be vulnerable to user enumeration to unauthenticated users through the GraphQL API. |
| CVE-2021-39906 | High | 2021-11-05 | Not applicable | Forecast only | Improper validation of ipynb files in GitLab CE/EE version 13.5 and above allows an attacker to execute arbitrary JavaScript code on the victim's behalf. |
| CVE-2021-22242 | High | 2021-08-25 | Not applicable | Forecast only | Insufficient input sanitization in Mermaid markdown in GitLab CE/EE version 11.4 and up allows an attacker to exploit a stored cross-site scripting vulnerability via a specially-crafted markdown |
| CVE-2021-22238 | Medium | 2021-08-20 | Not applicable | Forecast only | An issue has been discovered in GitLab affecting all versions starting with 13.3. GitLab was vulnerable to a stored XSS by using the design feature in issues. |
| CVE-2021-22175 | Critical | 2021-06-11 | Not applicable | Exploited | When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab affecting all versions starting from 10.5 was possible to exploit for an unauthenticated attacker even on a GitLab instance where registration is disabled |
| CVE-2021-22205 | Critical | 2021-04-23 | Not applicable | Exploited | An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. GitLab was not properly validating image files that were passed to a file parser which resulted in a remote command execution. |
| CVE-2020-13340 | High | 2020-10-08 | Not applicable | Forecast only | An issue has been discovered in GitLab affecting all versions prior to 13.2.10, 13.3.7 and 13.4.2: Stored XSS in CI Job Log |
| CVE-2020-2096 | Medium | 2020-01-15 | Mitigation candidate | Exploited | Jenkins Gitlab Hook Plugin 1.4.2 and earlier does not escape project names in the build_now endpoint, resulting in a reflected XSS vulnerability. |
| CVE-2019-5485 | Critical | 2019-09-13 | Not applicable | Working exploit published | NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability. Arbitrary commands can be injected through the repository name. |